Report computation
report_computationSay how a computation an issue rests on stands — a GAP run, a batch of work units, a Lean build that ran somewhere else; the tracker runs nothing. Call it when the job is submitted, as it progresses and when it ends, with the same 'source' + 'externalId' every time: that is one job, updated, never a second. Send only what you know now — a field left out keeps what an earlier report said, so a progress report need not repeat the commit. 'state' is queued, running, done, failed, cancelled or lost (a job whose runner stopped answering); 'starting' reads as running. Report the commit it ran at and the repository's web address: that is what makes a [computer] result checkable, and the answer's 'commitUrl' links it where the host is GitHub or GitLab. 'result' is what came of it, in a sentence — Markdown and $…$ formulas work. Say what it spent when you know it — 'machine', 'cores', 'cpuSeconds' (processor time so far, all cores together; send the running total each time, it is not added up), 'wallSeconds', 'gpuSeconds' — and always on the last report, a failed or cancelled job's included: that is what the issue's and the project's machine-hours and costs are counted from. A job on a service billed by the second (Modal: machine 'modal') also says 'memoryGiB' and 'gpuType' beside 'gpuSeconds', which its tariff prices; where you know what the service billed for the job, send 'costUsd' — it wins over the cost worked out from the price list. Answers with 'created' and 'stateBefore'. A name already reported on another issue is refused with that issue's key. Requires permission to edit the issue.
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": {
"key": "<key>",
"source": "<source>",
"externalId": "<externalId>"
},
"name": "report_computation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | The issue the computation answers, e.g. 'MATH-74'. | |
| url | No | The job's own page on its runner (http/https). | |
| cores | No | Cores allocated to it, e.g. 8 (or 0.5). | |
| state | No | queued, running, done, failed, cancelled or lost. | |
| title | No | What it computes, in words, e.g. 'rank 5, order 2^11, stage C'. | |
| commit | No | The commit it ran at. | |
| result | No | What came of it, a sentence or two. Markdown, $...$ formulas. | |
| source | Yes | Who runs it, e.g. 'tm' or 'boinc'. The job's name is unique within it. | |
| command | No | How it was run: the command line or the job's description. | |
| costUsd | No | What the service itself billed for the job, in US dollars, where you know it (Modal's billing report). It wins over the cost worked out from the price list. | |
| gpuType | No | The GPU's type, e.g. 'H100', 'A100-80GB', 'L4' — what a tariff prices a GPU-second by. | |
| machine | No | The machine it ran on, e.g. 'kimmy', 'ax42', 'modal'. | |
| memoryGiB | No | Memory allocated to it in GiB — billed by a tariff such as Modal's. | |
| outputUrl | No | Where its output can be fetched (http/https). | |
| startedAt | No | When it started (ISO 8601). Left out, a move to running stamps now. | |
| cpuSeconds | No | Processor time used so far, all cores together, in seconds — the running total, not an increment. | |
| externalId | Yes | The job's own name there, e.g. 'kimmy/gap/m74r5u'. The same name again updates the job. | |
| finishedAt | No | When it ended (ISO 8601). Left out, a move to a finished state stamps now. | |
| gpuSeconds | No | GPU time in seconds, where there was one. | |
| repository | No | The repository's web address, e.g. 'https://github.com/org/repo'. | |
| wallSeconds | No | Its wall clock in seconds, where the runner counts it otherwise than end minus start. | |
| progressDone | No | How much is done, as the runner counts, e.g. 812. | |
| progressTotal | No | Out of how much, e.g. 1695. |