List computations
list_computationsThe computations issues rest on, as their runners reported them: state, progress, the commit and repository, the job's page and output, and what came of it. With 'key', one issue's; with 'projectKey', the project's, newest first and the ones still going on top — state 'open' (queued or running) is what is going now, which is the first thing to ask after a lost session instead of reading status comments. 'state' may also be one of queued, running, done, failed, cancelled, lost. Each job carries what it spent — 'machine', 'cores', 'cpuSeconds', 'wallSeconds', and 'spend' worked out from them in seconds ('machineSeconds' is the measured CPU time, or cores × wall clock where none was measured, and then 'estimated' is true); with 'key', 'spend' also sums the issue's own jobs and those of the work under it (sub-tasks, an epic's stories). Each job's 'cost' says what it came to in US dollars and what that rests on — 'basis' 'reported' (the service's own bill, sent as costUsd), 'tariff' (Modal's tariff by the second) or 'share' (a share of one of our machines' monthly price by load: the core-hours it held at price ÷ (cores × hours in the month)); 'estimate' true where the machine's price is an estimate or its type was assumed; 'fx' the exchange rate a price in euros was converted at; 'usd' null with 'missing' ('price', 'gpuRate', 'rate') where it cannot be known — never a zero. 'spend.cost' sums them like 'spend'. The prices are list_machine_prices. A project's machine-hours and costs over a period are computation_hours.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_computations"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | One issue's computations, e.g. 'MATH-74'. | |
| limit | No | How many, for a project (default 50, max 200). | |
| state | No | Only this state, or 'open' for queued and running together. | |
| projectKey | No | A project's computations, e.g. 'MATH'. Ignored when 'key' is given. |