get_dictionary
The data dictionary: field meanings and caveats, metric notes, and analysis memos, plus the field roles and known nuance shapes ax1om brings by default. The first read to make before building analysis on a workspace’s data. Honest about coverage: it describes what is held today rather than fabricating a catalog for fields nobody has described. Read-only.
What it returns
The data dictionary for this org - field meanings and caveats, metric notes and analysis memos - alongside ax1om's base-tier field roles and the nuance shapes it already knows about.
Credential
An app session token, from an authenticated app.ax1om.ai session. Call it with only an API key and you get a plain refusal saying so, rather than a confusing 401.
Network call: yes. The full credential split is on authentication.
Example call
Most readers never write the protocol themselves: the agent does, once the server is connected. Both forms are the same call.
Use the ax1om MCP server.Call get_dictionary: the data dictionary: field meanings and caveats, metric notes, and analysis memos, plus the field roles and known nuance shapes ax1om brings by default.{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "get_dictionary", "arguments": {} }}The arguments object is whatever this tool's own input schema declares. An MCP client reads that schema from the server, so it is the server that answers for the exact shape rather than this page.