mcp-printable

Overview Schema Source Related Servers Discussions Admin

blender_render_turntable

Read-onlyIdempotent

Render a 3D object in a full turntable rotation to reveal details of cylindrical shapes that fixed angles miss. Customize steps per full turn and elevation for optimal views.

Instructions

N-angle turntable around one object. Use for cylindrical geometry (barrels, pins) where 4 fixed angles miss details.

steps=8 → every 45°, steps=12 → every 30°. elevation in degrees (negative=below).

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": {
      "object_name": "<object_name>"
    },
    "name": "blender_render_turntable"
  }
}

Input Schema

Name	Required	Description	Default
`zoom`	No
`steps`	No
`isolate`	No
`elevation`	No
`object_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.3Aug 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral details such as the step-to-angle mapping (steps=8 → every 45°, steps=12 → every 30°) and elevation semantics (negative=below), which go beyond the schema and annotations.

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 extremely concise, with every sentence providing useful information. It front-loads the purpose, then gives formula-like parameter details without any fluff.

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?

Given the moderate complexity (5 params, 1 required) and the read-only/idempotent annotations, the description covers the core purpose, usage scenario, and key parameter behaviors. It does not describe the output format, but that is likely implied by the tool name and sibling context.

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 0%, so the description must compensate. It explains steps and elevation but does not clarify zoom or isolate. These are common terms with defaults, but the description only partially bridges the gap for 5 parameters.

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 tool renders an N-angle turntable around a single object, with specific use cases for cylindrical geometry. The verb 'render turntable' and the scope 'around one object' distinguish it from sibling tools like cross-section or tiled rendering.

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?

Provides explicit when-to-use guidance: 'Use for cylindrical geometry (barrels, pins) where 4 fixed angles miss details.' This implies when the tool is appropriate, though it doesn't name alternative tools explicitly. The exclusion of non-cylindrical cases is clear enough.

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