Skip to content

query ​

4 tools — 4 read, 0 write.

ToolWhat it does
describe_schemareadList what this workspace contains — its collections, node types and the links between them — before writing a query.
find_by_namereadLook up a workspace object by its name — prefix and partial words work (e.g.
queryreadAnswer one question across collections, notes, tasks and meetings in a single call — filter, project, order and page, with no stitching.
search_datareadSearch the user's knowledge base — notes, collections, customer records, tasks and meeting transcripts — and get ranked results with source attribution.

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.

Docs as of 2026-08-31.