Blender Bridge

Install or repair Blender extension

ensure_blender_extension

DestructiveIdempotent

Install or repair the bundled Blender Bridge extension for the receiving Desktop's selected Blender installation. Can overwrite the bundled add-on and reload it; Desktop may be started to perform the action. Returns installation/control status. Use when setup identifies a missing or incompatible extension or the user requests repair, rather than as an unconditional step before modeling. get_setup_status checks readiness; restart_blender_with_extension explicitly relaunches Blender when needed.

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

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?

With destructiveHint=true and idempotentHint=true already in annotations, the description adds useful specifics: it can overwrite the bundled add-on, reload it, and may start Desktop to perform the action. It also says it returns installation/control status. This meaningfully supplements the annotations, though it could say more about what 'repair' changes.

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?

The description is front-loaded with purpose, then behavior, then return status, then usage and alternatives. Every sentence adds targeted information, and none repeats schema or annotation content unnecessarily.

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 tool with rich annotations and no output schema, the description supplies the needed completeness: what it does, side effects, return summary, when to invoke it, and which siblings to consider instead.

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 has zero parameters, so there are no parameter semantics for the description to cover; the baseline for this case is 4. The description correctly avoids introducing parameter details that do not exist.

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 names a specific verb (install or repair) and resource (bundled Blender Bridge extension) and scopes it to the receiving Desktop's selected Blender installation. It distinguishes the tool from nearby siblings by naming get_setup_status and restart_blender_with_extension.

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 states when to use the tool: setup identifies a missing or incompatible extension, or the user requests repair. It also says when not to use it, warning against treating it as an unconditional step before modeling, and points to the relevant alternatives.

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?