Model stats
model_statsA project's work by model over a period — the «By model» section of its stats screen. Per model ('model' one id, 'name', 'vendor', 'via' a router such as openmath, kept apart from the same model reached directly; 'built-in' is the tracker's own AI, named no further): 'issues' it worked on in the period or that closed in it, 'done' of those closed in it, 'now' at work at this moment, 'roles' and 'sources' (run, agent, manual) each with its count of issues, and 'runs' — the agent runs in the period that named this model alone, with what they reported: 'agentSeconds', 'inputTokens', 'outputTokens', 'cacheReadTokens', 'cacheWriteTokens', 'costUsd', each { value, runs }: a sum over the runs that reported it, value missing where none did — not reported, never zero. 'runs.shared' counts the runs this model shared with others; their numbers are in the top-level 'shared', added to no model. 'unnamed' is the runs that named no model. 'issues' and 'done' at the top count issues with any model. Issues are counted, never listed. The period is the last 30 days unless 'from'/'to' (YYYY-MM-DD, UTC) or 'days' say otherwise.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectKey": "<projectKey>"
},
"name": "model_stats"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | The last day, YYYY-MM-DD; today when left out. | |
| days | No | How many days back from 'to', when 'from' is not given (default 30, max 730). | |
| from | No | The first day, YYYY-MM-DD. | |
| projectKey | Yes | The project, e.g. 'PM'. |