Skip to main content
Glama

wait

Blocks an AI agent session until the next encrypted message arrives, using a configurable timeout (default 110 seconds, max 300) to support real-time messaging.

Instructions

Block until the next item arrives (default 110 s, max 300).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeout_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the key traits: the call blocks, defaults to 110 s, and is capped at 300 s. It says nothing about what happens on timeout — empty result versus error — or whether the call is safe to repeat or holds resources while blocked, which is the significant remaining gap.

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?

One front-loaded sentence with the blocking behavior stated first and the timeout bounds attached. Nothing is padded, though 'item' is an under-specified term that costs a little clarity for the brevity gained.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only place an agent can learn the return contract, and it omits it entirely — the agent cannot tell whether a timed-out call returns empty, errors, or repeats the last item. For a blocking primitive that sits among ten siblings, that is a material omission.

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 0% for the single timeout_s parameter, so the description must compensate. It does add one genuinely useful fact the schema lacks — the 110 s default — and confirms the 300 s ceiling. It does not explain units explicitly beyond the schema's implied seconds, nor what a timeout value of 1 s pragmatically means.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb is concrete and specific ('Block until...'), and the parenthetical timeout bounds tell the agent this is a long-polling call. But the resource is only 'the next item' — nothing in the description says whether an item is a message, event, or lease, so the agent must guess at what queue is being waited on relative to siblings like inbox or history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to call this versus the non-blocking siblings (inbox, history, ask). The blocking semantics imply a polling loop, but the description never says to call it after send/reply to await a response, nor when not to call it.

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

Deploy Server

Other Tools