Skip to main content
Glama

reply

Answer a message addressed to you in its topic, marking it read and waking the sender; use progress instead if you are still working.

Instructions

Answer a message addressed to you, in the same topic; the original is marked read and the sender is woken. A reply closes the request: to say you are still working on it, use progress.

Args: id: id of the message you answer. text: your complete answer (for refused or failed: the reason). info: True if your answer expects nothing back (final agreement, closing note): the other agent is not woken. vote: "agree" or "disagree" (review), optional. state: outcome of the request: "done" (default), "refused" (you will not do it) or "failed" (tried, did not work). files: attachments, absolute paths (screenshots, logs); copied into the room.

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>",
      "text": "<text>"
    },
    "name": "reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
infoNo
textYes
voteNo
filesNo
stateNodone

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.7
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "replyOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Goes well beyond the annotations, which only declare the generic mutation profile. It discloses real side effects the annotations cannot: the original message is marked read, the sender is woken, and `info=true` suppresses that wake-up. It also notes that files are copied into the room, which is non-obvious persistence behavior.

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?

Front-loaded with the action and its consequence, then the dispatching rule against `progress`, then a tidy Args block. Every sentence adds information; nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating, 6-param tool with no output schema and only generic annotations, this is sufficient: action, routing, side effects, state semantics and attachment handling are all covered. An agent can invoke it correctly without further inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does: it documents all six params, including defaults (`info`, `state`), the permitted `state` values, the `vote` value domain ("agree"/"disagree"), and that `text` must be the complete answer with a reason for refused/failed. That is meaning the bare schema titles do not convey.

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 message addressed to you) plus the scope constraint (same topic) and immediate side effects. It explicitly contrasts itself with the sibling `progress`, so an agent can pick between them without inspecting schemas.

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?

Gives an explicit when-not rule: "A reply closes the request: to say you are still working on it, use progress." The `state` param enumerates the allowed outcomes (done/refused/failed) so the agent knows which mode applies to its situation.

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