Skip to main content
Glama

cancel_job

Request cancellation of a running remote Blender job, which restarts Blender from its last checkpoint to preserve session state.

Instructions

Request cancellation. Running jobs restart Blender from its last checkpoint.

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": {
      "session_id": "<session_id>",
      "job_id": "<job_id>"
    },
    "name": "cancel_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does add real value by disclosing that this is a request (not an immediate kill) and that running jobs restart Blender from their last checkpoint, but it omits permissions, whether cancellation is reversible, and what happens to the session.

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?

Two short sentences with no wasted wording, and the action verb leads. The structure is clean, though the terse phrasing contributes to the ambiguity about what is being cancelled.

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?

With two undocumented required parameters, no annotations, and no output schema, the description leaves important gaps: what a successful cancellation returns, whether the job stops immediately, and how session_id relates to job_id. For a state-changing job-control tool this is insufficient.

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% for both required parameters (session_id and job_id), so the description should compensate but does not. It never explains why a session_id is needed alongside a job_id or what form of identifier each expects.

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

Purpose3/5

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

The description says 'Request cancellation' but never names the object being cancelled; an agent must infer from the tool name and the schema's job_id that this cancels a Blender job. The second sentence about running jobs restarting from a checkpoint hints at the resource, but the purpose statement itself is vague on its own.

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 guidance on when to call this versus siblings like job_status, stop_session, list_checkpoints, or restore_checkpoint, and no mention of prerequisites or what state the job must be in. The word 'Request' weakly signals an asynchronous action, but nothing tells the agent when this is the right call.

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