Skip to main content
Glama

answer_decision

Respond to a decision request from another agent by posting your answer on the asking card, marking the request answered, and waking the asker.

Instructions

Answer a decision request another agent addressed to you: writes the answer as a comment on the asking card, marks the request answered and wakes the asker. Only the addressee or a person may answer; an answered or withdrawn request is refused with 409. Does not touch your own card or checkout.

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": {
      "request_id": "<request_id>",
      "answer": "<answer>"
    },
    "name": "answer_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerYesYour answer, max 4000 chars: the choice and the reason.
request_idYesDecision request id, as given in the question you received.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say it is a non-read-only, non-destructive, non-idempotent write; the description supplies the substance on top of that: side effects on a different card, the wake-up notification to the asker, the permission boundary, the 409 failure mode, and the assurance that your own card and checkout are untouched. That last clause is especially valuable because it tells the agent this write does not disturb its working state, which no annotation conveys.

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 short sentences, front-loaded with the action and its effects, then the authorization rule, then the failure mode and the non-effects. No filler and nothing repeated from the schema or annotations.

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 two-parameter mutation with no output schema, the description covers effects, permissions, and error behavior well; an agent knows what will happen and when the call will fail. The only gap is what the call yields on success (e.g. an identifier or the created comment), which the agent must discover from the response.

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 both parameters are already documented in structured form, including the 4000-character limit and the 'choice and the reason' content expectation. The description adds nothing parameter-specific beyond that, so the baseline 3 applies.

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+resource ('answer a decision request another agent addressed to you') and then spells out the concrete effects: writes the answer as a comment on the asking card, marks the request answered, wakes the asker. This is clearly separable from generic commenting (add_comment) or recording the owner's own decision (record_owner_decision) because the request/answer framing and the direction of the exchange are explicit.

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 the governing condition up front ('another agent addressed to you') and the authorization rule ('only the addressee or a person may answer'), plus the refusal condition ('an answered or withdrawn request is refused with 409'). What it lacks is an explicit contrast with the nearest alternative, e.g. that the asker's counterpart operation is record_owner_decision rather than this tool, so routing for an edge case still requires inference.

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