Skip to main content
Glama

Ticket decide

ticket_decide
Destructive

Answer the choice a blocked AI work board ticket is waiting on, on behalf of the person you are talking to: pick one of the options the agent offered (option_key, as listed under decision_request by ticket_get) or give the decision in their own words (answer). Records a 'Decision:' comment, clears the question, and resumes the agent with that answer - the same as deciding on the board page. It raises a confirmation card first, whatever the session's autonomy: the person's click on that card is the decision, so propose exactly the answer they gave. Only use this when the person has actually made the choice; never decide for them. Refused when the ticket is not waiting on a decision. Identify the ticket by ticket_number or ticket_id.

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_decide"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerNoThe decision in the person's own words - required when no option_key is given, otherwise an optional note beside the chosen option.
ticket_idNoThe ticket UUID. Optional when ticket_number is given.
option_keyNoKey of the offered option the person chose. Omit when the answer is something else.
ticket_numberNoThe per-organisation ticket number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing concrete side effects: it records a 'Decision:' comment, clears the question, resumes the agent, and raises a confirmation card first regardless of the session's autonomy setting. The autonomy override and the 'propose exactly the answer they gave' constraint are exactly the kind of non-obvious behavior an agent must know before calling a destructive tool.

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-loads the action and the two input modes, then the side effects, then the safety constraint — a sensible order. It is dense but slightly redundant around the confirmation card ('the person's click on that card is the decision, so propose exactly the answer they gave' plus the later 'never decide for them'), costing a point.

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 destructive, non-idempotent mutation with no output schema, the description covers preconditions, side effects, human-in-the-loop behavior, and ticket identification. Minor gaps remain: error behavior for an invalid option_key and whether the tool returns the resumed agent state are not mentioned.

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: option_key must come from decision_request listed by ticket_get, answer is the free-form alternative, and the two are mutually exclusive in intent. It does not explain what happens when an option_key is stale or unknown, which keeps it below 5.

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 and resource (answer a decision a blocked work board ticket is waiting on) and immediately distinguishes the two input modes (option_key from decision_request vs free-form answer). An agent can tell this apart from ticket_get, ticket_comment, or decide_pending_action without opening any 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?

Explicitly names the precondition ('Only use this when the person has actually made the choice'), the prohibition ('never decide for them'), and the refusal condition ('Refused when the ticket is not waiting on a decision'). It also points to ticket_get/decision_request as the source of valid option_key values, which routes the agent to the right prerequisite call.

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.