Blender Bridge

Read current Blender scene

get_scene_state

Read-onlyIdempotent

Inspect the current scene in the receiving Blender and return structured scene_state with runtime metadata and a text summary. full defaults to true; false requests the compact scene-state form. Uses a pass-only Bridge probe and does not change scene objects or create a screenshot. Requires account access and a working receiving Bridge/Blender. Use before deciding how to edit a scene; get_blender_info is for version/protocol diagnostics and take_screenshot is for visible appearance.

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

Input Schema

Name	Required	Description	Default
`full`	No	Include full scene-state detail unless false; omitted defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / full / description

Added value: +"Include full scene-state detail unless false; omitted defaults to true."

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 declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description reinforces this by stating it uses a pass-only Bridge probe, does not change scene objects, or create a screenshot. It further adds prerequisites (account access, working receiving Bridge/Blender). It doesn't cover failure/latency behavior, so not a full 5 with annotations already carrying the safety profile.

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?

Three tight sentences, all load-bearing: purpose, parameter behavior, safety/prerequisites, and sibling routing. Front-loaded with the core verb and scope.

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?

No output schema exists, yet the description characterizes the return (structured scene_state with runtime metadata plus a text summary). Combined with prerequisites and the non-mutation guarantee, an agent has everything needed to invoke it correctly.

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?

Schema coverage is 100% and the schema already documents the 'full' boolean and its default. The description reinforces the semantics by contrasting the full form against the compact scene-state form, adding a little meaning beyond the schema without over-explaining.

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 and resource ('Inspect the current scene in the receiving Blender') and names the return artifact (structured scene_state with runtime metadata and text summary). It is clearly distinguished from siblings like get_blender_info and take_screenshot, which are explicitly called out.

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?

Gives explicit when-to-use ('Use before deciding how to edit a scene') and routes alternatives precisely: get_blender_info for version/protocol diagnostics, take_screenshot for visible appearance. Nothing 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?