Skip to main content
Glama

Ticket request review

ticket_request_review
Destructive

Ask a colleague to review the ticket's drafted plan: moves the ticket to 'awaiting_review' so the reviewer agent (or a human) critiques it before any execution. On a desk with no reviewer agent configured it routes straight to 'awaiting_approval' (the human approval gate) instead of parking unstaffed. Requires a drafted plan (ticket_draft_plan first). The optional note frames what you want the reviewer to focus on.

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": "ticket_request_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoWhat the reviewer should focus on.
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.1/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=false, but the description goes beyond them by disclosing the actual state transitions (awaiting_review, or awaiting_approval as a fallback) and the reason for the fallback ('instead of parking unstaffed'). That is genuinely useful behavioral context an agent cannot derive from the annotations. It does not, however, address what happens if review is rejected or whether a repeat call on an already-reviewing ticket is safe, which matters given idempotentHint=false.

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?

Three sentences, front-loaded with the action and outcome, with no filler. The parenthetical asides are informative rather than padding, though the description could be trimmed slightly by folding the prerequisite and note guidance together.

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

Completeness4/5

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

For a three-parameter mutation tool with no output schema, the description covers the prerequisite, the state outcomes, the fallback path, and the optional note. The remaining gap is the downstream lifecycle — what a returned or rejected review means for the ticket — which is arguably out of scope for this call.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters are already documented, setting the baseline at 3. The description adds only a light gloss on the note parameter ('frames what you want the reviewer to focus on') that largely restates the schema text, and says nothing extra about ticket_id versus ticket_number resolution.

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 concrete verb and resource ('Ask a colleague to review the ticket's drafted plan') and immediately names the resulting state ('moves the ticket to awaiting_review'). This distinguishes it clearly from ticket_draft_plan (the prerequisite that produces the plan) and from a submit/decide step, so an agent can select it without inspecting the schema.

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

Usage Guidelines4/5

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

It gives an explicit precondition ('Requires a drafted plan (ticket_draft_plan first)') and explains the alternative routing path when no reviewer agent is configured, which is exactly the conditional an agent needs. It stops short of naming when not to use it — e.g. versus ticket_submit_review or ticket_decide — so it is clear context without full exclusion guidance.

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.