Blender Bridge

Choose connection and computer

set_connection

DestructiveIdempotent

Choose local for Blender on this computer, or remote with a listed device_id for another computer or a shared session. Read get_connection first; review the returned scope before another change.

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": {
      "mode": "<mode>"
    },
    "name": "set_connection"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	Yes	Use local for this computer or remote for an account/shared computer in a native plugin; hosted connectors support remote only.
`device_id`	No	Own or approved shared computer identifier returned by connection discovery.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedInput schema / properties / device_id / description

Added value: +"Own or approved shared computer identifier returned by connection discovery."

addedInput schema / properties / mode / description

Added value: +"Use local for this computer or remote for an account/shared computer in a native plugin; hosted connectors support remote only."

First observedOct 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the agent knows this is a scoped mutation. The description adds a procedural caution to review the returned scope before another change, but it does not explain what gets changed/destroyed, permission requirements, or session impact.

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?

Two sentences with no filler. The mode choice is front-loaded, and the prerequisite is placed immediately after, making the call sequence clear.

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?

For a two-parameter tool with full schema coverage, rich annotations, and no output schema, the description supplies the key prerequisite and post-change check. It is mostly complete, though a destructive connection-setting tool could do more to explain the practical impact of changing scope.

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 schema itself documents both mode and device_id in detail. The description reinforces the local/remote distinction and that device_id must be listed, but adds little semantic detail beyond what the schema already provides.

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

Purpose4/5

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

The description uses a specific verb ('Choose') and resource ('connection/computer'), and explains the two mode choices: local for this computer, remote with a listed device_id. It distinguishes itself from get_connection by requiring that tool first, though it does not explicitly differentiate from close siblings like select_computer or select_blender.

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?

It gives an explicit prerequisite: 'Read get_connection first' and 'review the returned scope before another change.' That tells the agent when to call it and what to check, but it does not state when not to use it or how it compares to alternatives such as check_connection or select_computer.

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?