Skip to main content
Glama

Ticket submit review

ticket_submit_review
Destructive

Deliver 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

NameRequiredDescriptionDefault
verdictYesThe review verdict.
rationaleYesWhy - the critique itself (markdown).
ticket_idNoThe ticket UUID. Optional when ticket_number is given.
ticket_numberNoThe per-organisation ticket number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only flag destructiveHint=true and non-idempotence; the description goes far beyond them by spelling out the state machine (awaiting_review → awaiting_approval → executing, or back to planning), that the rationale is mandatory and lands on the timeline, and the two refusal conditions. That explains the destructive, non-idempotent profile rather than contradicting it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and verdicts, then the state consequences and refusals. It is dense and the final sentence chains three separate constraints, but every clause carries decision-relevant information, so little could be cut without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a state-changing review tool with no output schema, the definition covers what to pass, what happens on each verdict, who is barred from calling it, and where the rationale appears. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it expands the verdict enum into decision criteria and reinforces that rationale is mandatory critique content, not an optional note. It says nothing extra about ticket_id versus ticket_number, which the schema already covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Deliver a peer-review verdict on the ticket's plan') and immediately enumerates the two verdicts plus the criteria behind each, so an agent can tell this apart from ticket_decide or ticket_request_review without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states explicitly when to use each verdict ('approve' when blast radius, rollback and verification are covered; 'request_changes' when naming gaps), and adds exclusion rules: human approval cannot be recorded here, an approve from an interactive chat session is refused, and the assignee cannot review its own plan.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.