Add summary
add_summaryFiles a handover summary of a task's progress, capturing done, remaining, blockers, and next step for the case file.
Instructions
Files a summary: the handover note of a case, in four parts, none of them empty
(entry_fields_invalid lists the empty ones).
A significant step is a decision made, a finished part of the work, a failure that changes the plan, or any point where a colleague would need an explanation of where the work stands.
Its index title is the first line of done, returned in the response. The final
summary, with unmeasured, is filed by close_task.
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>",
"done": "<done>",
"remaining": "<remaining>",
"blockers": "<blockers>",
"next_step": "<next_step>"
},
"name": "add_summary"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Task key `PROJECT-N`, case-insensitive; a previous key of a moved task addresses it as well. An unknown key is refused with `task_not_found` | |
| done | Yes | What was done since the previous summary, with references to artifacts. Its first line becomes the entry title in the case index: one sentence about what happened; a longer line is cut at a word boundary | |
| blockers | Yes | What stands in the way, or `nothing`. In a summary before a wait in `open` it names what is awaited, from whom, and its carrier: a `blocking` question or `blocked_by` | |
| next_step | Yes | The one concrete action a successor starts with. In a summary before a wait in `open` it is the action taken once the awaited arrives. A doubt about a decision or a result is recorded here, as what to look at and why, rather than as a verdict | |
| remaining | Yes | What remains before the task is done | |
| idempotency_key | No | Retry key chosen by the caller, e.g. a UUID. A repeat with the same key and the same arguments returns the first result and creates nothing; the same key with other arguments is refused with `idempotency_key_reused`. A key is bound to the caller's token and kept for 24 hours |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| no | Yes | Entry number in the task's case; with the key it forms `TRK-42#12` | |
| seq | Yes | Journal sequence number, usable as `after` of `wait_journal` | |
| title | Yes | The title the tracker built, for entry types whose title is not sent (summary, answer, verdict, resolution, service entries); `null` when the caller sent the title | |
| author | Yes | ||
| task_key | Yes | ||
| created_at | Yes |