protein-blender-mcp

render_image

Render the current Blender scene from the camera to preview styling or save a final image by disabling preview and providing an output path.

Instructions

Render the scene from the camera and return the image so you can check the styling. preview=True renders at 50% size for speed; set preview=False and give a path for the final figure.

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

Input Schema

Name	Required	Description	Default
`path`	No
`preview`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the side effect of writing an output file when a path is given and the cost tradeoff of preview mode (50% size for speed), which is genuinely useful. However, it doesn't state what happens if preview=False is set without a path, whether the image is returned as data or only written to disk, or what format is produced.

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?

Two sentences, front-loaded with the action and outcome, followed by the mode guidance. Every clause carries information an agent needs to pick the right invocation.

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 two-parameter render tool with no output schema, this covers purpose, the preview/path tradeoff, and the intended inspection workflow. The remaining gaps are around return-value shape and error behavior when path is omitted, which are minor for a tool of this complexity.

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 0%, so the description must compensate, and it largely does: it explains that preview=True renders at 50% size for speed and that preview=False should be paired with a path for the final figure. This covers both parameters and their interaction, though the default-null path behavior when preview=False is not spelled out.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Render the scene from the camera') and names the observable outcome ('return the image so you can check the styling'). It implicitly distinguishes itself from setup siblings like frame_camera and set_render_settings by being the step that produces the image, though it never names an alternative explicitly.

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?

Gives concrete workflow context: use it to check styling, use preview=True for fast iteration, and switch to preview=False with a path for the final figure. What's missing is any guidance on prerequisites (camera must be framed) or when to use this versus execute_blender_python for custom rendering.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server