Blender Bridge

Save reference and render comparison

compare_reference_render

Save one PNG with the active camera reference photo on the left and the latest PNG/JPEG render on the right, preserving aspect ratios. Render an image first. Does not match perspective or alter the scene/source images. Existing outputs are refused.

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": {
      "operation_name": "<operation_name>"
    },
    "name": "compare_reference_render"
  }
}

Input Schema

Name	Required	Description
`filename`	No	Output filename for this result; choose a name appropriate to the requested format.
`max_side`	No	Maximum side length of the saved comparison image, in pixels.
`project_name`	No	Project name used to organize this output in the receiving Desktop workspace.
`project_path`	No	Absolute project folder only when the user explicitly supplied this external destination. Otherwise use Desktop’s configured workspace.
`operation_name`	Yes	Short, concrete history title in the user's language describing the requested operation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 23, 2026

addedInput schema / properties / filename / description

Added value: +"Output filename for this result; choose a name appropriate to the requested format."

addedInput schema / properties / max_side / description

Added value: +"Maximum side length of the saved comparison image, in pixels."

addedInput schema / properties / operation_name / description

Added value: +"Short, concrete history title in the user's language describing the requested operation."

addedInput schema / properties / project_name / description

Added value: +"Project name used to organize this output in the receiving Desktop workspace."

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: it preserves aspect ratios, does not match perspective, does not alter the scene or source images, and refuses existing outputs. These details clarify side effects, limitations, and overwrite behavior for a write operation.

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 short and front-loaded: it states the core output first, then the prerequisite, then the non-mutation caveat and overwrite refusal. Every sentence contributes useful information with no filler.

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 non-read-only tool with rich annotations and full schema coverage but no output schema, the description covers the essential context: what is saved, the layout, the prerequisite render, non-perspective-matching limitations, source-image preservation, and refusal of existing outputs.

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 all five parameters. The description does not add parameter-level meaning such as filename handling, max_side behavior, or project path semantics, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: it saves one PNG containing the active camera reference photo on the left and the latest render on the right. This clearly distinguishes the tool from siblings like render_project_image or take_screenshot by describing a composite side-by-side output rather than a render or screenshot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear prerequisite ('Render an image first') and a clear refusal condition ('Existing outputs are refused'). It does not explicitly name alternative tools or explain what to do when an output already exists, but the usage context is otherwise well defined.

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?