create_database needs a workspace ID, and list_databases returns the databases across every workspace your token reaches, each tagged with the workspace it belongs to.
How the assistant works with your data
A few things shape the results you get. It reads the schema first.get_schema returns the authoritative reference for field types, their options, and the operators available for filtering. A well-behaved assistant calls it before creating tables or fields and before building a filter, rather than guessing.
Field keys are IDs, not column names. A record comes back keyed by field ID, not by the label you see in the table. list_fields maps between the two, which is why the assistant may look up a table’s fields before it can talk about a record in your terms.
Some fields cannot be written to. Formula, lookup, rollup, and count fields are computed from other data. Created time, updated time, created by, updated by, autonumber, and record ID are managed by Softr. The assistant can read all of them but cannot set them, and cannot change a field’s type after it is created.
Nothing can be deleted (yet, will be possible soon). There is no tool to delete a record, table, field, or database. Removing data is something you do in the builder.
Schema
Databases
Tables and fields
Records
Analytics
aggregate_data returns totals rather than rows, which makes it the right tool behind questions like “revenue by month” or “how many open tickets per assignee”. It groups by at most two fields.
Limits
Asking for more than 200 records is not an error — you simply get 200. Reading a large table therefore takes several calls, which is another reason to prefer a filter or an aggregate over paging through everything.