Skip to main content
Glama

render_viewport

Capture the current Houdini 3D viewport to an image file, with optional camera, resolution, and settle delay so Karma views can converge before capture.

Instructions

Capture the current 3D viewport to an image file.

Args: output_path: Image file path; variables ($JOB) are expanded. Default: a new PNG in the temp dir. resolution: [width, height] in pixels. Default: the viewport's own size. camera: Camera node path. settle_seconds: Wait this long before capturing, without blocking Houdini, so a Karma viewport can converge after a change. Use this instead of a shell sleep between calls. Capped at 120.

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

Input Schema

NameRequiredDescriptionDefault
cameraNo
resolutionNo
output_pathNo
settle_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / output_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / output_path / default
      Added value: +null
    • removedInput schema / properties / output_path / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "output_path"
      -]
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose useful traits: the wait does not block Houdini, settle_seconds is capped at 120, and $JOB variables are expanded in output paths. It omits what an agent would still want to know about a file-writing tool, such as whether an existing file is overwritten, whether the directory must exist, and what the call returns.

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?

The purpose statement is front-loaded and the Args block maps one-to-one onto the four parameters with no filler. The multi-line wrapping of the settle_seconds entry is slightly verbose but every sentence adds information rather than restating the schema.

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?

For a four-optional-parameter, no-annotation, no-output-schema tool, the description covers purpose, all parameters, defaults, and the non-blocking wait behavior. The remaining gap is the post-capture result, since there is no output schema to explain whether a file path or status is returned.

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 0%, so the description is the only source of parameter meaning, and it documents all four: output_path (variable expansion, default new PNG in temp dir), resolution as [width, height] with a viewport-size default, camera as a node path, and settle_seconds with its purpose and 120 cap. Only minor gaps remain, such as the exact camera path syntax and any validation on resolution length or bounds.

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 first sentence states a specific verb and resource: "Capture the current 3D viewport to an image file." An agent can immediately tell this is a viewport screenshot tool rather than a node-graph or full render tool. It does not explicitly distinguish itself from siblings like capture_screenshot or render_quad_view, so it stops short of a 5.

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

Usage Guidelines3/5

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

Guidance is present but narrow: settle_seconds is framed as the alternative to "a shell sleep between calls" for letting Karma converge, which is genuinely actionable. However, there is no statement of when to use this versus capture_screenshot, render_quad_view, or get_viewport_info, and no prerequisites or exclusions. Usage is implied from purpose rather than spelled out.

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