Blender Bridge

Cancel Blender operation

cancel_blender_operation

DestructiveIdempotent

Cancel a Blender Bridge operation by request id. Background renders stop their owned Blender process immediately. Queued work is skipped; other already-running Blender Python uses cooperative cancellation.

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": {
      "request_id": "<request_id>"
    },
    "name": "cancel_blender_operation"
  }
}

Input Schema

Name	Required	Description	Default
`reason`	No	Optional explanation for the cancellation request.
`request_id`	Yes	Queued or running operation identifier to cancel.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026
- addedInput schema / properties / reason / description
```
Added value: +"Optional explanation for the cancellation request."
```
- addedInput schema / properties / request_id / description
```
Added value: +"Queued or running operation identifier to cancel."
```
First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already flag destructive=true and idempotent=true, and the description goes well beyond them by disclosing the differential cancellation semantics: immediate process termination for background renders, skipped queued work, and only cooperative cancellation for other running Blender Python. That is exactly the kind of outcome detail an agent needs before calling a destructive tool.

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?

Three short sentences, front-loaded with the action and key, with the cancellation semantics following. No filler or repetition.

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?

Covers the essentials for a cancel tool with no output schema: what is cancelled and how abruptly. It does not say what happens when the request_id is unknown or already complete, nor whether a status is returned, which leaves a small gap.

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 100%, so both request_id and the optional reason are already documented in the schema. The description only reinforces that request_id identifies a queued or running operation and says nothing about the reason parameter or id format, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb (cancel) and resource (Blender Bridge operation) plus the keying parameter (request id). An agent can distinguish it from get_blender_operation_status or stop_bridge from the description alone.

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

Usage Guidelines4/5

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

Explains the effect depending on operation state (background render, queued work, running Python), which implicitly tells the agent when this tool is applicable. It never explicitly excludes cases or names a sibling alternative, so it stops short of full routing guidance.

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

All Blender Bridge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?