check_validation
The scoring-vs-outcomes check-in: cohort conversions by score band for a model’s live scores, with maturity honesty. Cohorts too young to grade say so, showing counts and withholding rates, rather than rendering noise. The natural week-2 and week-4 questions: are the top bands converting, and is it too early to tell?
Read it before you tell anyone the model is working. That is the week-2 and week-4 check-in: are the top bands converting, and is it too early to tell? Both are real answers.
What it needs
| Argument | Type | Required | Description |
|---|---|---|---|
model_id | string | Yes | |
maturity_days | integer | No |
What it returns
How the scored records actually performed - outcomes by score band for the predictions that have matured, the counts behind every band, and what is still too early to grade.
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 check_validation: the scoring-vs-outcomes check-in: cohort conversions by score band for a model’s live scores, with maturity honesty.{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "check_validation", "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.
Notes
- Cohorts too young to grade say so and return counts with the rates withheld, rather than rendering noise as a trend.