Skip to main content
Glama

render_thumbnail_to_path

Destructive

Render a thumbnail from the active Blender camera to a specified file path for scene previews and documentation.

Instructions

Render a small image from the active camera to output_path.

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": {
      "output_path": "<output_path>"
    },
    "name": "render_thumbnail_to_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNo
blend_fileNo
output_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/overwrite risk is flagged structurally. The description adds that the image comes from the active camera and is 'small' (thumbnail-sized), but says nothing about overwriting an existing file at output_path, permissions, or what happens if the scene has no active camera.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with the action and destination front-loaded and no filler. It is efficient, though the terseness borders on under-specification for a three-parameter tool.

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

Completeness2/5

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

An output schema exists, so return values need no explanation, but for a destructive, three-parameter tool with zero schema coverage the description is too thin. An agent cannot tell what blend_file does or whether writing to output_path clobbers an existing file.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, yet it only references output_path. The timeout and blend_file parameters — the latter clearly non-trivial for a Blender tool — are left entirely unexplained in both schema and description.

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?

The description names a specific verb (render) and resource (a small image from the active camera), and the phrase 'from the active camera' implicitly distinguishes it from the sibling render_viewport_to_path. It stops short of explicitly naming or excluding that alternative, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternatives guidance. The agent must infer from 'active camera' versus 'viewport' which render tool is appropriate, and nothing tells it when a thumbnail render is preferable to a full render or screenshot call.

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