Skip to main content
Glama

wait_reply

Waits up to 600 seconds for replies to sent messages and returns them, keeping each answer reserved for the requesting session so no other session receives it.

Instructions

Wait for the answer to a message you sent (600 s max) and return it; it is marked read. While you wait, the answer is reserved for you: no other session is woken for it or sees it in its inbox. Status "restarting": the relay is switching to new code; call again (the answer is kept for you). Returned without an answer (timeout, unavailable): the one that arrives later is attached (late_replies) to your next call, then marked read. Status "cancelled": you cancelled the request. Several ids (send to a list): waits for all of them; status "success" once all answered, otherwise "partial" (or the common status); replies gives each one's result in order.

Args: id: id returned by send, or the list of ids (send to several recipients). timeout_s: maximum wait in seconds (1 to 600, default 300).

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

Input Schema

NameRequiredDescriptionDefault
idYes
timeout_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.8.7
    • addedInput schema / properties / id / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  }
      +]
    • removedInput schema / properties / id / type
      Removed value: -"string"
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "wait_replyOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations, disclosing reservation semantics (answer is held for the caller), the 'restarting' retry case, late_replies attachment behavior on timeout or unavailability, 'cancelled' status, and multi-id 'partial' aggregation. These are non-obvious behavioral traits an agent could not infer from readOnlyHint=false alone. The description is consistent with the mutation implied by marking messages read.

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?

The core behavior and timeout are front-loaded, then edge cases (restarting, timeout, cancelled, multi-id) are enumerated compactly. It is slightly dense with status casework, but each sentence conveys a distinct behavior rather than restating the name.

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?

With no output schema, the description still sketches return shape — status values, replies in order, late_replies — enough to interpret results. A full field-by-field return contract is absent, but for a two-parameter blocking call the coverage is adequate.

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 0%, so the description must carry the load, and it does: id is 'the id returned by send, or the list of ids', and timeout_s is bounded 1–600 with default 300, adding the range the schema omits. The multi-id list semantics and their effect on status/replies are explained, though id format specifics are not.

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 — wait for the answer to a message you sent and return it — plus the 600 s ceiling and the side effect of marking it read. It is clearly distinguishable from siblings like inbox, read, and send because it describes an active blocking wait tied to an id.

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?

Explains the key selection context: while waiting, the answer is reserved for you and no other session sees it in its inbox, which implicitly tells the agent why to prefer this over polling inbox. It does not explicitly name alternatives or exclusions, so it stops short of a full routing rule.

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