list_nuances
What ax1om knows about this workspace’s data semantics, merged across two tiers: universal CRM truths, and this workspace’s own entries. Every entry is labeled with its tier and status, and only confirmed entries ever affect a number. A fresh workspace sees the base tier rather than an empty list. Read-only.
What it needs
| Argument | Type | Required | Description |
|---|---|---|---|
subject_kind | any | No | |
subject_key | any | No |
What it returns
The nuance entries that apply to this org, merged across ax1om's base tier and the org's own, each labelled with its tier and whether it is confirmed or only proposed.
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 list_nuances: what ax1om knows about this workspace’s data semantics, merged across two tiers: universal CRM truths, and this workspace’s own entries.{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "list_nuances", "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.