Skip to main content
Glama

render_preview

Render a preview image of the current Blender scene using adjustable samples and resolution percentage to check lighting, materials, and composition before final rendering.

Instructions

Render a fast preview image.

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_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
samplesNo
resolution_percentageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/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, yet it discloses almost nothing: not whether a file is written, whether it blocks until completion, or what 'fast' costs in quality. The output schema covers return values, but the mutation/side-effect profile of the call remains undeclared.

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 short sentence with no wasted wording and the key scope word ('fast') front-loaded. It is efficient, though the brevity borders on under-specification rather than genuine economy.

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?

With two undocumented parameters, no annotations, and no sibling differentiation, the definition leaves too much for the agent to infer even though the output schema relieves it of explaining return values. It should at minimum state the quality/speed tradeoff and when a preview is preferable to a full render.

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 needed to compensate and does not mention samples or resolution_percentage at all. The phrase 'fast preview' loosely gestures at the quality/speed knobs, but a caller has no explanation of what samples or resolution percentage do beyond the bare property names and defaults.

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 gives a specific verb (render) plus resource (preview image) and adds a scope qualifier ('fast') that hints at the speed/quality tradeoff versus a final render. It does not explicitly name or differentiate itself from render_final or render_scene, so the distinction is inferred rather than stated.

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 or when-not-to-use guidance; nothing tells the agent to prefer this over render_final, render_scene, or capture_render, or in what workflow stage a preview is appropriate. 'Fast preview' implies a rough-quality use case but leaves the choice among siblings entirely to inference.

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