Blender Bridge

Panel: choose connection route

view_set_route

DestructiveIdempotent

App-only adapter for a native Desktop plugin workspace's Local/Remote selector. Changes only that workspace's route and epoch; a foreground write blocks switching. mode selects the transport and device_id identifies a listed Remote computer. Review the returned scope before the next write. A fixed hosted connection does not support native transport switching. Models should use set_connection; the panel uses view_select_computer to change a computer without changing transport.

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

Input Schema

Name	Required	Description	Default
`mode`	Yes	Connection mode for this native workspace.
`device_id`	No	Listed Remote computer identifier when selecting a specific target.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedInput schema / properties / device_id / description

Added value: +"Listed Remote computer identifier when selecting a specific target."

addedInput schema / properties / mode / description

Added value: +"Connection mode for this native workspace."

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already disclose that this is destructive, non-read-only, idempotent, and closed-world. The description adds useful behavioral context beyond them: it changes only the workspace route and epoch, a foreground write blocks switching, and the caller should review the returned scope before the next write.

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?

The purpose and key constraints are front-loaded, and the alternative-tool routing is clearly stated. Some phrases are dense and panel-specific, but every sentence contributes useful selection or behavior information.

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 panel adapter with annotations and no output schema, the description covers the scope, constraints, and alternatives adequately. The only minor gap is that 'returned scope' is not further described, though no output schema is available.

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 the schema already documents both parameters, including the mode enum. The description adds only modest clarification that mode selects the transport and device_id identifies a listed Remote computer.

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?

The description states a specific verb and resource: it changes a native Desktop plugin workspace's Local/Remote route and epoch. It also distinguishes this panel adapter from the model-facing set_connection tool and from view_select_computer, so the agent can tell what this tool is for without opening the sibling schemas.

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?

It explicitly says models should use set_connection, while the panel uses this tool and view_select_computer for different changes. It also gives a when-not condition: a fixed hosted connection does not support native transport switching.

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?