Skip to content

list_models

MCP server · Discover

What this workspace already has, so an agent can triage from the listing instead of pulling full results for every model: status, the run currently serving, whether a quality reading exists yet, where the training data came from, and how many warnings the last run raised. Status is a workflow state a person set, not a quality verdict, and a row that looks approved while carrying warnings says so. Read-only.

What it needs

ArgumentTypeRequiredDescription
include_archivedbooleanNo

What it returns

Every model this org can call, each with its family, its status, the run currently serving, whether a quality reading is available yet, where its training data came from, and how many warnings its last run raised.

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.

prompt
Use the ax1om MCP server.
Call list_models: what this workspace already has, so an agent can triage from the listing instead of pulling full results for every model: status, the run currently serving, whether a quality reading exists yet, where the training data came from, and how many warnings the last run raised.

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.

Need help?Contact supportLatest changes?See the changelog
Something wrong?Check system statusComing soon