Skip to main content
Glama

swarm_wait

Pause an agent until a new board message arrives, consuming zero tokens while waiting; specify the last seen sequence and optional mention-only or timeout criteria.

Instructions

Sleep until a new message is posted to the board. Consumes zero tokens while sleeping.

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": {
      "since": "<since>"
    },
    "name": "swarm_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceYesHighest message sequence number the caller has seen.
callerNoOptional caller roster name override.
mentions_onlyNoWake only for messages mentioning this agent, @all, or @#channel.
timeout_secondsNoMaximum seconds to wait before returning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the call blocks and is token-free while waiting, which is real behavioral value. It does not say what is returned on timeout, whether the wait is server-side long-polling versus client retry, or any concurrency/rate constraints.

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?

Two short sentences, front-loaded with the core behavior and followed by the key efficiency property. Nothing is redundant or padded.

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 simple blocking wait with a fully documented schema, the definition covers the essential behavior and the token-cost benefit. The main gap is the absence of an output schema combined with no statement of what the call yields on wake versus timeout, which an agent must know to use the result correctly.

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 100%, so all four parameters (since, caller, mentions_only, timeout_seconds) are already documented with defaults. The description adds no syntax or semantic detail beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

States a specific action and resource: block/sleep until a new message appears on the board. An agent can tell this is a wait/blocking primitive rather than a read or post operation, though the description never names the sibling read_board it is implicitly contrasted with.

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

Usage Guidelines3/5

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

The phrase 'sleep until a new message is posted' implies the use case (waiting for new activity instead of polling), and 'consumes zero tokens' hints at why to prefer it over repeated reads. However, there is no explicit when-to-use/when-not guidance and no named alternative such as read_board or post_message.

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