Skip to main content
Glama

Answer a proposed change

answer_run

Answers a run from ask_reedapt that is waiting (status needs_input): "apply" makes the proposed change, "decline" drops it. Only apply what the person has seen and agreed to. Applying voices the changed lines again.

Instructions

Answers a run from ask_reedapt that is waiting (status needs_input): "apply" makes the proposed change, "decline" drops it. Only apply what the person has seen and agreed to. Applying voices the changed lines again.

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": {
      "run_id": "<run_id>",
      "choice": "<choice>"
    },
    "name": "answer_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
choiceYes
run_idYesThe run's id, from ask_reedapt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description goes beyond them by disclosing the precondition, the meaning of each branch (apply mutates, decline discards), and a non-obvious side effect (applying voices the changed lines again). Nothing contradicts the annotations, since an apply of an already-proposed change is not destructive.

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 clauses, front-loaded with the trigger condition and the branch semantics, with no filler or restated field names. Each sentence carries distinct information.

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 definition covers trigger, branch behavior, a safety constraint, and a side effect. It stops short of saying what is returned or what happens on a stale/invalid run_id, which is the only remaining gap.

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 only 50% and the enum values carry no schema description, so the description has to supply their semantics: "apply" commits the proposed change and "decline" drops it. That is real added meaning, though run_id is left entirely to the schema.

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 ("Answers a run from ask_reedapt") plus the exact precondition (status needs_input), and distinguishes itself from the sibling that creates the run. An agent can tell immediately what this tool does relative to ask_reedapt.

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 says explicitly when to call it: only for a run that is waiting with status needs_input, and adds a behavioral constraint ("Only apply what the person has seen and agreed to"). It does not spell out what to do if the run is not in that state, but the context is unambiguous.

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