Blender Bridge

Stop Desktop bridge

stop_bridge

DestructiveIdempotent

Stop the receiving Desktop's Bridge service when the user wants to end that connection or agrees to recovery. This interrupts Bridge-based tool connections and can interrupt in-flight requests; it does not delete scene/project files or request a Blender restart. Returns stopped/control status. Use start_bridge to bring the service back. Prefer get_app_state or check_connection for passive inspection: this control action can start Desktop first if its control service is unavailable.

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": "stop_bridge"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only say destructiveHint=true and idempotentHint=true; the description supplies the substance behind that flag — it interrupts in-flight requests, does NOT delete scene/project files, and does not force a Blender restart. It also discloses the non-obvious side effect that the control action may start the Desktop first if its control service is unavailable, which an agent could not predict from structured fields.

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?

Front-loaded with the action and the main interruption caveat before alternatives, and every sentence carries information. It is slightly dense at ~75 words with three distinct concerns (effects, return, alternatives) packed into consecutive sentences, but none are filler.

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?

No output schema exists, and "Returns stopped/control status" is the only, somewhat vague, statement about the response shape. Everything else an agent needs — consent condition, blast radius, reversibility via start_bridge, side effect — is present and specific.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and a baseline 4 applies. No parameter-level claims are made that need correcting.

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 and resource ("Stop the receiving Desktop's Bridge service") and immediately scopes it against related operations. An agent can distinguish it from start_bridge, get_app_state, and check_connection without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit trigger conditions ("when the user wants to end that connection or agrees to recovery") and names three alternatives with the conditions selecting them: start_bridge to restore, get_app_state/check_connection for passive inspection. Nothing is left to inference.

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?