Blender Bridge

Select Blender installation

select_blender

DestructiveIdempotent

Save the Blender executable that the receiving Desktop should use for subsequent actions. path identifies an existing compatible Blender 4.2+ executable on that computer. Changes a persistent selection and can start Desktop if its control service is unavailable. Returns selection/control status. Discover choices with find_blender_installations; open_blender is the separate launch action. Use only when the user wants to change the selected installation.

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": {
      "path": "<path>"
    },
    "name": "select_blender"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Path to the selected Blender 4.2+ executable on the receiving computer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / path / description

Added value: +"Path to the selected Blender 4.2+ executable on the receiving computer."

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true; the description adds non-obvious behavior beyond them — the selection is persistent, and the call may start Desktop when the control service is down — plus that it returns selection/control status. It doesn't spell out that the prior selection is overwritten or any permission/validation failure modes, which keeps it from a 5.

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?

Five short sentences, each carrying distinct information: the mutation, the path constraint, side effects, sibling routing, and the selection condition. The usage exclusions are placed at the end as a guard rather than buried mid-text.

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?

For a one-parameter mutation tool with no output schema, the description covers preconditions (existing compatible 4.2+ binary), side effects (persistent change, possible Desktop start), and what is returned. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100% and the single parameter is already documented as the path to a Blender 4.2+ executable. The description repeats the compatibility constraint ('existing compatible Blender 4.2+ executable on that computer') without adding format, quoting, or validation details, 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 and resource ('Save the Blender executable that the receiving Desktop should use') and explicitly separates itself from find_blender_installations (discovery) and open_blender (launch). An agent can identify the operation without opening the 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 an explicit when-to-use condition ('Use only when the user wants to change the selected installation') and names both relevant alternatives with their distinct roles. Nothing is left to inference about routing.

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?