Skip to main content
Glama
Sign In
Unity MCP Claude Code

Unity MCP Claude Code

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

blender_render_preview

Renders a headless Blender preview of 3D models (GLB/FBX/OBJ) to generate a PNG image, enabling visual validation of generated or imported assets.

Instructions

Rendert eine Vorschau-PNG eines 3D-Modells (GLB/FBX/OBJ) headless in Blender (CYCLES) — damit Claude generierte/importierte 3D-Assets per Bild prüfen kann.

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": {
      "model_path": "<model_path>",
      "output_png": "<output_png>"
    },
    "name": "blender_render_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_pathYes
output_pngYes
widthNo
heightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A4/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations by specifying headless rendering using CYCLES engine. It does not contradict annotations (readOnlyHint=false, destructiveHint=false). It could mention prerequisites like Blender installation or side effects, but overall adequate.

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 two sentences, front-loading the core purpose and usage context. Every word serves a purpose with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's purpose but omits details on return values, prerequisites (e.g., Blender installed), and how to interpret the output. Given no output schema, more completeness is needed for an AI agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain any parameters. With 0% schema description coverage, the description should compensate but fails to provide meaning for model_path, output_png, width, or height.

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 clearly states the action (renders a preview PNG), the resource (3D model in GLB/FBX/OBJ formats), and the context (headless in Blender CYCLES). It differentiates from siblings like blender_bake_pbr by focusing on preview rendering for visual inspection.

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?

The description provides clear context for use: to check generated/imported 3D assets via image. However, it lacks explicit guidance on when not to use or alternatives among sibling tools, such as using blender_bake_pbr for baking.

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

Deploy Server

Other Tools