Skip to main content
Glama

Ticket draft plan

ticket_draft_plan
Destructive

Write or revise the ticket's plan document: the markdown remediation/execution plan reviewers critique and humans approve. Include the proposed change, blast radius, rollback strategy, and verification steps. Drafting (or re-drafting after changes were requested) sets the plan state to 'drafted'; follow with ticket_request_review to invite the peer reviewer.

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": {
      "plan": "<plan>"
    },
    "name": "ticket_draft_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesThe full plan document (markdown). Replaces the previous revision; the old text stays in the timeline.
ticket_idNoThe ticket UUID. Optional when ticket_number is given.
plan_actionsNoOptional: the action classes this plan will use, as [{"tool": "restart_deployment", "namespace": "payments"}]. Declare every step that changes something. A desk whose organisation has opted those action classes into unattended execution, and whose assignee runs at autonomy 'auto', can then start executing without a human click; a plan that declares nothing, or that names one step outside the trusted set, waits at the human approval gate exactly as before.
ticket_numberNoThe per-organisation ticket number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description discloses the concrete state transition to 'drafted' and the sequencing that follows, which an agent cannot infer from the hints alone. It does not explain what happens on a failed write or whether concurrent drafting is rejected, but the destructive hint is already qualified by the schema note that prior revisions remain in the timeline.

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

Conciseness5/5

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

Three tight sentences: identity and scope first, content requirements second, state and next step last. No filler, no restatement of the title, and the workflow cue is front-loaded at the end where it is most actionable.

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 write tool with full schema coverage and no output schema, the definition covers purpose, required content, resulting state, and the next step in the workflow. It could add a note on error or validation behavior, but nothing essential for a correct invocation 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 for the 'plan' parameter by enumerating required content: proposed change, blast radius, rollback strategy, and verification steps. It leaves the ticket_id/ticket_number resolution and plan_actions autonomy behavior to the schema, which documents them fully.

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?

States a specific verb pair ('write or revise') and a precisely scoped resource ('the ticket's plan document'), then defines what that document contains. It also distinguishes itself from ticket_request_review by naming it as the next step rather than an alternative for the same job.

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?

Gives clear context for when to call it — drafting a first plan or re-drafting after changes were requested — and explicitly names the follow-up tool (ticket_request_review) with its purpose. It does not state any when-not conditions, such as what to do if a plan already exists and is awaiting approval.

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.