Skip to main content
Glama

Get swarm subagent task status

swarm_status
Read-only

Check the non-blocking status of cb_*, sess_*, or qd_* tasks and automatically reconcile dead worker processes.

Instructions

Non-blocking status check for any cb_* or sess_* task, reconciling dead worker processes automatically.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only and closed-world profile, and the description adds two things they don't: the call never blocks, and it automatically reconciles dead worker processes. The reconciliation disclosure is valuable because it tells the agent stale entries get cleaned up on read; it sits in mild tension with readOnlyHint since it implies bookkeeping side effects, but the operation is substantively a read.

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?

A single front-loaded sentence that leads with the most important trait (non-blocking) and then the scope. No filler, nothing redundant with the schema or annotations.

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 one-parameter read tool with annotations, the coverage is close to sufficient. But with no output schema, the description gives no hint of what a "status" contains (state, progress, exit code), which is the main thing an agent needs before calling a status endpoint.

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 taskId parameter, so the description has to carry the load. It partially does by naming valid task prefixes (cb_*, sess_*), but omits the qd_* form the schema allows and says nothing about whether the id must be a live task.

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 verb+resource ("Non-blocking status check") scoped to cb_* and sess_* tasks, which an agent can distinguish from swarm_wait and swarm_result. The only weakness is that it enumerates task prefixes incompletely: the schema pattern also permits qd_*, so the stated scope is narrower than the real one.

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?

"Non-blocking" is a real routing signal that implies this is the poll-don't-block counterpart to a waiting tool, so usage is inferable. However, no alternative is named and there is no explicit when-not-to-use guidance (e.g. when to prefer swarm_wait or swarm_result).

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