Blender Bridge

Check Bridge and Blender connection

check_connection

Read-onlyIdempotent

Test whether the receiving Desktop Bridge and Blender add-on are reachable, authenticated and compatible for work. Returns readiness, component/contract details and a concrete blocker when the local runtime is unavailable. Does not execute a scene command or launch Blender. Use after a connection failure; get_connection instead lists account computers and session access, while get_setup_status provides the broader setup diagnosis.

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

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

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds useful context: it returns readiness, component/contract details, and a concrete blocker when the runtime is unavailable. It also explicitly bounds scope with 'does not execute a scene command or launch Blender', which is a valuable non-behavior not captured by annotations.

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?

Four sentences, each earning its place: purpose first, then return contract, then explicit negative scope, then sibling routing. Front-loaded and free of repetition.

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 zero-parameter read-only diagnostic with annotations and no output schema, the description supplies everything needed: what it checks, what it returns, what it does not do, and how it relates to sibling tools. No gaps that would cause incorrect invocation.

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 document beyond the input schema; baseline 4 applies. The description correctly reflects a no-argument diagnostic tool.

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 ('Test') applied to well-defined resources (Desktop Bridge and Blender add-on) with the exact conditions checked: reachability, authentication, compatibility. The description distinguishes the tool from get_connection and get_setup_status, so an agent can select it without inspecting siblings.

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?

Explicitly states when to use it ('after a connection failure') and names the alternatives with their distinct roles: get_connection lists account computers and session access, get_setup_status gives the broader setup diagnosis. Clear routing guidance with no exclusions left implicit.

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?