Skip to main content
Glama

render_viewport_to_path

Destructive

Render the active camera view to a specified output path using the scene's render settings to produce image or animation outputs for review or export.

Instructions

Render from the active camera to output_path using the scene's render settings.

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_viewport_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 destructiveHint=true and readOnlyHint=false, so the write/overwrite risk is flagged structurally. The description adds real context — it renders from the active camera under the scene's render settings — but says nothing about overwriting an existing file at output_path, how the output format is chosen (extension vs. scene settings), or what timeout governs. Useful but incomplete beyond the annotations.

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 destination and camera source front-loaded and no filler. It is efficient, though its brevity leaves the gaps noted in other dimensions.

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 not be described, but this is a destructive file-writing operation with zero parameter documentation and no overwrite warning, no format determination hint, and no explanation of blend_file or timeout semantics. The risk of silently clobbering a file makes the omission material rather than cosmetic.

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% across three parameters, so the description must compensate and largely does not: it only echoes output_path, whose name is already self-explanatory. Neither timeout (default 120, units? blocking? failure behavior?) nor blend_file (implies rendering a file other than the currently open one) is clarified anywhere.

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?

"Render from the active camera to output_path using the scene's render settings" gives a concrete verb plus source (active camera) and destination (output_path), which distinguishes it in spirit from render_thumbnail_to_path. It stops short of naming that sibling or stating the contrast explicitly, so an agent must infer the difference from 'active camera' versus 'thumbnail'.

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 guidance and no mention of the obvious alternative (render_thumbnail_to_path) or of preconditions such as whether a blend file must be open or supplied. The agent gets no rule for choosing between the two render tools or for when to pass blend_file.

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