Appearance
Domains
Grouping collections, and views that read across them.
7 tools — 4 read, 3 write.
| Tool | What it does | |
|---|---|---|
create_domain | write | Create a domain — a named grouping of collections (e.g. |
delete_domain | write | Delete a domain. |
export_domain_view | read | Export a SAVED domain (spine) view as a CSV snapshot: the view's own filters, column selection and column order, every row it resolves to. |
list_domains | read | List the domains (collection groupings) you can see in this organization, with how many collections each groups. |
modify_domain | write | Rename a domain and/or set its description. |
preview_domain_view | read | Render an UNSAVED domain (spine) view config without persisting it: one row per item in the config's anchor collection, one column per relation path walked out from it. |
resolve_domain_view | read | Render a domain (spine) view: one row per item in the view's anchor collection, plus one column per relation path walked out from it. |
Calling these
Over MCP, find one with search_tools, then run it with execute_tool. Over REST, POST /api/capabilities/<tool> with the arguments as the JSON body. Either way, fetch the input schema for the tool you're about to call rather than guessing — get_tool_schema over MCP, or GET /api/capabilities?name=<tool> over REST.
See How the API works for auth, errors and the shared envelope.