Skip to main content
Glama

body_stop_all

Cancel all running background tasks and close open contracts immediately as a panic stop. Halts in-flight work only, without touching your files.

Instructions

STOP EVERYTHING: cancel the running background tasks and close the open contracts.

This is the panic button - it never touches your files, only the work in flight.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "body_stop_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoemergency stop

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it declares the blast radius as in-flight work only, explicitly excluding files. It leaves open whether stopped work is resumable or undoable and what state tasks end in, which is the remaining gap.

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 short sentences, both front-loaded: impact first, safety boundary second. No wasted wording.

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

Completeness4/5

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

For a one-parameter, no-output-schema emergency tool, the definition covers impact scope and safety adequately. The only real omission is guidance on the 'reason' argument.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single 'reason' parameter (default 'emergency stop') has 0% schema description coverage and is never mentioned in the description, so an agent learns nothing about whether to supply a custom reason or what it is used for. The description should have compensated for the coverage gap and does not.

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 scope: 'cancel the running background tasks and close the open contracts,' with 'STOP EVERYTHING' signalling global rather than per-item scope. This implicitly separates it from narrower siblings like body_task_cancel or body_console_stop, though it never names them.

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?

'This is the panic button' gives an implied emergency-use context, and the 'never touches your files' line bounds what it affects. It stops short of saying when NOT to use it or pointing at the per-task cancel alternatives for selective stopping.

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