Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

render_viewport

Captures the current 3D viewport to an image file with options for output path, resolution, camera, and a non-blocking settle delay for Karma convergence.

Instructions

Capture the current 3D viewport to an image file.

Args: output_path: Image file path. Default: a new PNG in the temp dir. resolution: [width, height] in pixels. 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.

Input Schema

TableJSON 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

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure itself. It does add real value: the non-blocking nature of settle_seconds ('without blocking Houdini'), the 120 second cap, and the default output behavior (new PNG in temp dir). It does not disclose what is returned, whether an existing file is overwritten, or whether a viewport must exist.

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?

Front-loaded one-line summary followed by a compact Args block; every entry earns its place. The indented multi-line entry for settle_seconds is slightly verbose but justified by the non-obvious behavior it documents.

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

Completeness3/5

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

With no output schema and no annotations, the description is adequate for calling the tool but incomplete on outcomes: it never says what is returned or how failures (no visible viewport, invalid path) are surfaced. Family-level routing cues for capture vs render tools are also absent.

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 description coverage is 0%, so the description must compensate, and it largely does: all four parameters are documented, including the [width, height] format for resolution, the meaning of camera as a node path, and the semantics plus cap for settle_seconds. It adds meaning well beyond the bare schema, though camera path syntax and resolution bounding are only loosely specified.

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?

States a specific verb+resource: 'Capture the current 3D viewport to an image file.' An agent can tell what it does, but the description never distinguishes it from near-siblings like capture_screenshot, render_quad_view, or capture_network_editor, which an agent must choose between.

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?

The only usage guidance is parameter-scoped: settle_seconds says 'Use this instead of a shell sleep between calls.' There is no guidance on when to prefer this tool over other capture/render tools, nor any prerequisite (e.g. a viewport must be open) for invoking it.

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