Skip to main content
Glama

check_worker

Check a running worker’s output and status, with heartbeat mode for lightweight status and line-based options for incremental output review.

Instructions

Check the output and status of a running worker. Use heartbeat=true for lightweight status without output content.

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>",
      "featureId": "<featureId>"
    },
    "name": "check_worker"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNoNumber of lines of output to capture (default: 50)
featureIdYesID of the feature whose worker to check
heartbeatNoReturn lightweight status only (no output content) - saves context
sinceLineNoReturn only output after this line number (for incremental updates)
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a read-only operation and mentions a context-saving mode, but says nothing about what happens when the worker is not running, whether output is truncated or buffered, or what 'status' actually contains — significant gaps for a monitoring tool with zero annotation coverage.

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 sentences, front-loaded with the core action and followed by the one non-obvious usage tip. No filler, no redundancy, and the most important operational detail is placed where it will be read.

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?

With five parameters, no output schema, and no annotations, the description is thinner than the tool's complexity warrants. Because no output schema exists, the description should at least sketch what 'output and status' returns and how lines/sinceLine interact with it, which it does not.

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 the five parameters are already documented in the schema, establishing a baseline of 3. The description's heartbeat note largely restates the schema text ('Return lightweight status only (no output content) - saves context') and adds no semantics for lines, sinceLine, featureId, or projectDir beyond what the schema provides.

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 pair ('check the output and status of a running worker'), which is concrete and immediately actionable. It implicitly distinguishes itself from check_all_workers by scoping to a single worker, but never names that sibling or any other, so differentiation relies on the reader noticing the singular phrasing.

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 sentence about heartbeat=true gives a concrete mode-selection hint (lightweight status vs. output content), which is useful. However, there is no guidance on when to use this versus check_all_workers or get_worker_confidence, and no statement of prerequisites such as the worker actually being in a running state.

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