Skip to main content
Glama
worker-mcp
by noosxe

Terminate a worker

terminate_worker
DestructiveIdempotent

Stop a worker and remove it, freeing its name and slot under the worker limit. Use it when done with a worker or to clear one that has wedged; in-flight runs end as cancelled.

Instructions

Stop a worker and remove it, freeing its name and its place under the worker limit. Call it when you are done with it, or to clear one that has wedged. A run in flight ends as cancelled; results of its runs stay readable with get_run for a while.

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": {
      "workerId": "<workerId>"
    },
    "name": "terminate_worker"
  }
}

Input Schema

NameRequiredDescriptionDefault
workerIdYesThe worker (id or name).

Output Schema

NameRequiredDescriptionDefault
workerIdYes
closedRunsYesRuns ended by the termination.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description goes well beyond that by naming exactly what is destroyed (the worker, its name, its slot under the limit), what happens to work in progress ('a run in flight ends as cancelled'), and what survives (run results stay readable with get_run, with a retention caveat of 'for a while'). This is precisely the extra context annotations cannot express.

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?

Three short sentences, front-loaded with the action and its consequences, then usage guidance, then downstream effects. No filler or repetition of the title, and every clause carries information an agent needs.

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

Completeness5/5

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

With one well-documented parameter, an output schema, and rich annotations, the remaining burden on the description is behavioral — and it covers mutation effects, in-flight run handling, and post-termination read access. Nothing material an agent needs to invoke this destructively-irreversible tool correctly is absent.

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?

There is a single parameter at 100% schema coverage, and the schema already documents that it accepts either an id or a name. The description's mention of 'freeing its name' hints at name-based addressing but adds no new format or constraint information. Baseline 3 is appropriate when the schema fully carries parameter semantics.

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

Purpose5/5

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

The description gives a specific verb and resource pair ('Stop a worker and remove it') and states the two concrete side effects — the name and the worker-limit slot are freed — which distinguishes it from run-level operations like cancel_run or get_run in the sibling list. An agent can tell what this tool does and what it operates on without opening the schema.

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

Usage Guidelines4/5

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

'Call it when you are done with it, or to clear one that has wedged' gives two clear triggering conditions, and the pointer to get_run implicitly steers agents to read run results there instead of keeping the worker alive. What's missing is an explicit when-not (e.g. use cancel_run to stop a single run while keeping the worker), but the positive guidance is concrete.

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