Skip to main content
Glama

body_task_cancel

Cancel a running background task so execution stops at the next step boundary.

Instructions

Cancel a background task (it stops at the next step boundary).

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": {
      "task_id": "<task_id>"
    },
    "name": "body_task_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add one genuinely useful trait: cancellation is not immediate but takes effect at the next step boundary. It says nothing about what happens to an unknown or already-finished task_id, whether the call is idempotent, what the response contains, or any permission requirement.

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?

A single front-loaded sentence with no filler; the key behavioral caveat is placed immediately in parentheses rather than buried.

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?

The tool is simple (one required string, no output schema, no annotations), so the bar is modest, and the step-boundary caveat is a good addition. Still, an agent cannot tell from this definition how to obtain a task_id or how this differs from adjacent cancel/stop tools, which are the two gaps that matter most here.

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?

Schema description coverage is 0%, so the single task_id parameter is documented nowhere. The description does not say where a task_id comes from (presumably from body_task_start), what format it takes, or what an invalid id produces, so it leaves the only input fully ambiguous.

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 ('Cancel a background task') so the operation is unambiguous, and the parenthetical clarifies it targets a long-running background task rather than a foreground/blocking call. It does not explicitly separate itself from lookalike siblings such as body_cancel or body_stop_all, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing says how this differs from body_cancel or body_stop_all, nor what preconditions exist (e.g. the task must be running). The only content beyond the name is a behavioral note about where cancellation takes effect, which is not usage routing.

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