Skip to main content
Glama

cancel

Stops a queued or rendering ComfyUI job using its ID, letting you halt unwanted video generation and free your local GPU for other work.

Instructions

Stops a queued or rendering job.

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": {
      "id": "<id>"
    },
    "name": "cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so safety framing is partly covered. The description adds nothing about what stopping does to partial render output, whether the cancellation is reversible or restartable, or what the response reports — the questions an agent actually faces before mutating a job.

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?

One short sentence, front-loaded with the verb and no filler or redundant restatement of the title. It is efficient, though so terse that it borders on under-specification rather than economical phrasing.

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

Completeness2/5

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

For a state-mutating tool with an undocumented identifier, no output schema, and no annotations describing effects, the description does not cover enough: the id space, post-cancel job state, and effect on partial output are all absent. An agent must guess before invoking.

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 required parameter "id" has 0% schema description coverage and the description never says what kind of id it is (job id vs. download id vs. video id) or where to obtain it. With a sibling named cancel_download that plausibly takes a similar id, the ambiguity is material rather than trivial.

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?

"Stops a queued or rendering job" gives a specific verb (stops) plus the resource and the states it applies to, so an agent can tell this mutates job lifecycle rather than video content. It does not name or contrast with the sibling cancel_download, leaving the two cancel-family tools to be disambiguated from the name alone.

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 phrase "queued or rendering" implicitly bounds when the tool is applicable (a job still in flight), which is a real usage condition. Beyond that there is no guidance on prerequisites, what happens for already-finished jobs, or why one would choose cancel over delete_video or cancel_download.

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