Blender Bridge

Open Blender

open_blender

Destructive

Launch the Blender installation selected in the receiving Desktop application when the user wants to work in Blender. Requires that computer and Desktop to be available with active account access. Desktop can install or update its bundled Blender extension before launching; repeating the call can open another window. Returns launch status, not a screenshot or a completed scene. Use get_setup_status to check readiness and open_blender_view to open only the chat panel.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Adds real context beyond the annotations: the Desktop may install or update its bundled Blender extension before launching, repeat calls open additional windows (consistent with idempotentHint=false), and the return is launch status rather than a screenshot or finished scene. It does not, however, explain what the destructiveHint=true actually covers, which is the one behavioral fact an agent most needs before calling.

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 purpose and prerequisites, then alternatives, then return shape; every sentence carries distinct information. Slightly dense at five clauses, but no sentence is filler.

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

Completeness5/5

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

With no output schema and no parameters, the description supplies exactly what is missing: prerequisites, side effects (extension install, multiple windows), the shape of the return value, and the alternative tools. An agent has enough to call it correctly without further context.

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?

Zero parameters, so there is no per-parameter semantics to convey; the baseline of 4 applies. The description correctly implies the target installation is whatever was previously selected rather than being passed as an argument.

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 (launch) and resource (the Blender installation selected in the receiving Desktop application), plus the user intent that triggers it. It is immediately distinguishable from open_blender_view (chat panel only) and get_setup_status (readiness check), which are explicitly named.

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 when-to-use ("when the user wants to work in Blender"), prerequisites (computer and Desktop available with active account access), and two named alternatives with their selecting conditions (get_setup_status for readiness, open_blender_view for panel-only). Agent routing is fully determined.

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?