Blender Bridge

Load packaged test scene

run_test_scene

Destructive

Load a packaged Blender Bridge demonstration scene in the receiving Blender after the user requests a test. scene_id selects logo (default) or cube. This changes the current scene and can replace existing contents; preserve user work before using it. Requires account access and a working paired Bridge/Blender. Returns the scene-operation result and request metadata. Use get_scene_state or check_connection for inspection without loading a demonstration; this tool is not needed before ordinary modeling.

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

Input Schema

Name	Required	Description	Default
`scene_id`	No	Packaged demonstration to load; omitted defaults to logo.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026
- addedInput schema / properties / scene_id / description
```
Added value: +"Packaged demonstration to load; omitted defaults to logo."
```
First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotency, but the description adds real context: scene contents can be replaced, user work should be preserved first, and it requires account access plus a working paired Bridge/Blender. It also states it returns the scene-operation result and request metadata, though it does not discuss undo/reversibility or blocking behavior.

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 tight sentences, front-loaded with the action and selector, followed by the destructive warning, prerequisites, and alternatives. No filler or redundant repetition of the tool name.

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 one-parameter destructive mutation tool with no output schema and rich annotations, the description covers trigger, scope, side effects, and prerequisites. Minor gaps remain around whether the operation is synchronous and how to recover from an unwanted scene replacement.

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 enum parameter is fully documented with its default. The description only restates the logo/cube choice and default, adding no new syntax, constraints, or edge-case semantics beyond the schema.

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 ('Load a packaged Blender Bridge demonstration scene') and names the selector values ('logo (default) or cube'). It is immediately distinguishable from siblings like get_scene_state or check_connection, which it explicitly frames as inspection-only alternatives.

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 gives an explicit trigger ('after the user requests a test'), explicit alternatives for inspection ('Use get_scene_state or check_connection'), and an explicit exclusion ('this tool is not needed before ordinary modeling'). Little is left to inference.

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?