Skip to main content
Glama

handoff_answer

Idempotent

Writes the reply under a waiting handoff note and marks it done or declined with a timestamp, then pushes it through git sync so the sender can read the answer back.

Instructions

For the agent that ANSWERS notes (a sender never calls this): writes the reply under ## Reply, sets the status to done (or declined, when it will not do it) and the answered time, and pushes it when the desk syncs through git. Only a waiting item can be answered; a repeat changes nothing. Never put passwords, codes or keys in a reply.

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": {
      "id": "<id>",
      "reply": "<reply>"
    },
    "name": "handoff_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
replyYes
statusNodone

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.4

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations: it discloses the exact write target ('under `## Reply`'), that status and answered-time are also mutated, that the change is pushed when the desk syncs via git, and that non-waiting items are rejected. The 'a repeat changes nothing' claim is consistent with idempotentHint=true, and the secrets warning adds safety context the annotations do not carry.

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, front-loaded with the caller restriction, then effects, then preconditions, then the safety caveat. Nothing is repeated or filler.

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 mutating tool with no output schema, the description covers effects, state transitions, idempotency, sync behavior and a security constraint — enough to call it correctly. It leaves the failure/return surface implicit, which is a minor gap rather than a blocking one.

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?

With 0% schema description coverage the description must carry the load, and it does: it defines where `reply` lands, gives the semantic condition for `status` ('declined, when it will not do it'), and implies `id` must reference a waiting item. It does not mention the 8000-character reply limit or what an invalid/non-waiting id produces, so it is not fully compensating.

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?

Names a specific verb and resource ('writes the reply', 'sets the status') and scopes the caller explicitly ('For the agent that ANSWERS notes (a sender never calls this)'). An agent can tell this apart from the send-side siblings 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 Guidelines4/5

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

States a hard precondition — 'Only a waiting item can be answered' — and clarifies the no-op case 'a repeat changes nothing'. It does not name an alternative tool (e.g. for reading before answering), so it stops short of full routing guidance, but the when-to-use condition is unambiguous.

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