Ticket submit review
ticket_submit_reviewDeliver a peer-review verdict on the ticket's plan: 'approve' (the plan is sound - blast radius understood, rollback exists, verification defined) or 'request_changes' (name the gaps). The rationale is mandatory and lands on the timeline. Approving as a peer agent advances an awaiting_review ticket to awaiting_approval (human sign-off), a human approval releases the ticket to executing, and requesting changes returns it to planning. Human approval cannot be recorded through this tool: an 'approve' from an interactive chat session is refused (the human approves on the AI board), and the assignee cannot review its own plan.
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": {
"verdict": "<verdict>",
"rationale": "<rationale>"
},
"name": "ticket_submit_review"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| verdict | Yes | The review verdict. | |
| rationale | Yes | Why - the critique itself (markdown). | |
| ticket_id | No | The ticket UUID. Optional when ticket_number is given. | |
| ticket_number | No | The per-organisation ticket number. |