Skip to main content
Glama

check_all_workers

Retrieves the status of all active workers at once, returning a consolidated summary with optional terminal output snippets for monitoring parallel coding sessions.

Instructions

Check status of all active workers at once. Returns a consolidated summary with optional output snippets.

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": {
      "projectDir": "<projectDir>"
    },
    "name": "check_all_workers"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format: 'compact' for minimal output (no emoji/decorators), 'pretty' for full formatting (default)
heartbeatNoUse heartbeat mode for all workers (lightweight, no output)
projectDirYesAbsolute path to the project directory
outputLinesNoNumber of output lines per worker (default: 10)
includeOutputNoInclude terminal output snippets (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 burden. It discloses the return shape (a consolidated summary with optional output snippets) and 'check' implies a read-only operation, but it says nothing about whether any worker state is touched, how expensive the fan-out is, or what happens when no workers are active.

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 short sentences with the scope front-loaded and no filler. Slightly under-informative rather than padded, which is the better failure mode.

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?

Parameters are fully covered by the schema and this is a read-only status check, but with no output schema the description should do more to characterize the 'consolidated summary' — what per-worker status fields or aggregate counts the agent can expect.

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 five parameters are already documented in the schema, establishing the baseline. The description reinforces only the includeOutput behavior via 'optional output snippets' and adds nothing about format, heartbeat, or outputLines.

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 and resource: 'Check status of all active workers at once,' plus what it returns. The 'all ... at once' scope implicitly distinguishes it from the singular check_worker sibling, though it never names an alternative explicitly.

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?

No explicit when-to-use or when-not guidance, and no alternative tool is named. The bulk scope ('all active workers at once') only implies that this is the batch counterpart to the individual check, leaving the agent to infer the selection rule.

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