describe_connection
The columns of one object on a connection: each with its type, the role schema discovery graded it, whether it reads as personal data, and how populated it is; the other objects you can describe; and, for the uploaded-CSV workspace, its upload history. Read-only. This is the read that lets an agent learn a workspace's schema without provoking a validation error to see it.
What it needs
| Argument | Type | Required | Description |
|---|---|---|---|
connection_id | string | Yes | |
object_name | any | No |
What it returns
The columns of one object on this connection - each with its type, the role schema discovery graded it, whether it reads as personal data, and how populated it is - the other objects available to describe, and for the uploaded-CSV workspace its upload history.
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 describe_connection: the columns of one object on a connection: each with its type, the role schema discovery graded it, whether it reads as personal data, and how populated it is; the other objects you can describe; and, for the uploaded-CSV workspace, its upload history.{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "describe_connection", "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.