Skip to main content
Glama

Wait for any swarm subagent task

swarm_wait
Read-only

Blocks until a cb_* or sess_* subagent task reaches a terminal state or timeoutSec elapses, then returns its status and final result.

Instructions

Block until a cb_* or sess_* task reaches a terminal state or timeoutSec elapses (default 45, max 55). Returns status and final result when complete.

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

Input Schema

NameRequiredDescriptionDefault
taskIdYes
timeoutSecNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds the critical behavioral fact that the call blocks, plus a default (45s) and hard ceiling (55s) on the wait. It stops short of saying what is returned when the timeout elapses rather than the task completing.

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?

Two tight sentences with the blocking semantics and timeout bounds front-loaded; nothing is padded. The only waste is the prefix enumeration, which is both partial and duplicative of the schema pattern.

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

Completeness3/5

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

For a blocking tool with no output schema, saying it returns status and final result is a reasonable sketch, but the timeout path is left ambiguous: an agent cannot tell whether a timeout raises an error or returns a non-terminal status. The missing qd_* task form also leaves a valid input unexplained.

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%, so the description has to carry parameter meaning. It supplies the timeoutSec default (45) and max (55) that the schema's bare minimum/maximum do not express, but it describes taskId only as cb_* or sess_*, omitting the qd_* form the schema pattern accepts.

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?

Names a specific action (block until terminal state) and the resource (a cb_* or sess_* swarm task), and states the two exit conditions. It does not differentiate itself from the sibling wait tools (hub_wait, zcode_wait) or explain why to block here rather than poll swarm_status/swarm_result, so sibling differentiation is only partial.

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?

Usage is implied by 'Block until ... terminal state', which suggests it is the tool for waiting on an in-flight task. There is no explicit statement of when to prefer this over swarm_status, swarm_result, or the sibling wait tools, and no guidance on what to do after a timeout.

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