Skip to main content
Glama

body_cancel

Request cancellation of a running task or a specific task_id. The executor stops at the next step boundary and reports CANCELLED without pretending the work was done.

Instructions

Request cancellation of the running task (or a specific task_id).

Cancellation is cooperative: the executor stops at the next step boundary and reports CANCELLED. It never pretends the cancelled work was done.

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

Input Schema

NameRequiredDescriptionDefault
task_idNo

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 present, the description carries the full burden and does a good job disclosing the key behavior: cancellation is cooperative, takes effect at the next step boundary, and reports CANCELLED rather than silently pretending work completed. It omits other operational facts such as idempotency, what happens when nothing is running, and permission requirements.

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?

Three short lines, front-loaded with the action and target, with the behavioral caveat following. The final sentence largely restates the cooperative-cancellation point, so it is slightly redundant but not padded.

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 tool with no output schema, the definition covers the essential semantics of cooperative cancellation. It still leaves gaps an agent would care about: what the response looks like, behavior on an unknown or already-finished task, and how it relates to body_task_cancel and body_stop_all.

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 optional task_id parameter, so the description must compensate. It does partially, by indicating that omitting task_id targets "the running task" and supplying it targets a specific one, but it never states the accepted ID format or the empty-string default behavior.

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 concrete verb+resource ("Request cancellation of the running task") and names the optional task_id target, so the agent can tell what will be affected. However, a near-identical sibling (body_task_cancel) exists and the description does nothing to distinguish this tool from it, leaving the agent without a reason to prefer one over the other.

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?

Usage is implied: call this to stop the running task, optionally passing a task_id. There is no explicit when-not guidance (e.g. what to do if no task is running) and no reference to the similarly named sibling, so the agent must guess at routing.

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