Skip to main content
Glama

Preview Render (Viewport, Constant Lines)

preview_render

Render a sketch-style preview of the scene for quick verification. Returns a base64 PNG; supports preset views or a named camera.

Instructions

Quick agent-friendly verification render. Uses the Viewport renderer with the active editor view temporarily switched to Constant Shading (Lines) — sketch-style and fast. Independent of the active RenderData (built freestanding, never inserted) and restores BaseDraw / camera / time / take in finally. Returns a base64 PNG inline so the agent can directly view it. Use view: top|bottom|left|right|front|back for an auto-framed temp camera, or camera to render through a named scene camera. Pass save_path to also write the PNG to disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
takeNoOptional take name to switch to before rendering. Restored afterward.
viewNoPreset view. 'current' (default) uses the active BaseDraw camera. The other presets place a temp camera looking at the scene bounds from that side; the temp camera is removed in finally.
frameNoOptional frame number; defaults to the current document time.
widthNoOutput width in pixels (default 1024, max 4096).
cameraNoOptional scene camera object name. Mutually exclusive with a non-'current' view.
heightNoOutput height in pixels (default 1024, max 4096).
save_pathNoOptional absolute PNG path. When set, the rendered image is also written to disk (parent directory must already exist). The base64 PNG is still returned inline.
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: it temporarily switches view to constant shading, builds freestanding RenderData (not inserted), restores BaseDraw/camera/time/take in finally, returns base64 PNG, and explains view/camera mutual exclusivity. No contradictions.

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 a single paragraph of four sentences, front-loaded with purpose and key behavior. Every sentence provides necessary detail without redundancy.

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

Completeness5/5

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

Despite no output schema or annotations, the description covers all important aspects: the rendering pipeline, parameter behavior, return format, and side effects (save_path). It addresses edge cases like view/camera exclusivity and temporary camera lifecycle, making it complete for this tool.

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 100% and each parameter has a description. The description adds value by explaining the behavior behind the parameters (e.g., view presets auto-frame a temp camera, camera mutual exclusion, width/height defaults and max). This goes beyond the bare schema.

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 it is a quick agent-friendly verification render using Viewport with constant shading lines, sketch-style and fast. It distinguishes itself from the sibling 'render' tool by being a lightweight preview.

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 says it is for quick verification renders, implying use for previews rather than final output. It does not explicitly state when not to use it or direct to alternatives like the sibling 'render' tool, which would have strengthened the guideline.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kumoproductions/mcp-cinema4d'

If you have feedback or need assistance with the MCP directory API, please join our Discord server