Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

frame_all

Frame all Houdini viewport geometry, or focus the camera on specific nodes or world-space bounds.

Instructions

Frame all geometry in the viewport, or only some nodes or a box.

Args: pane_name: Pane tab name. node_paths: Frame just these objects or SOPs (their world bounds), not the spread of everything in the scene. An object frames what it draws: a null its marker, a camera or a light its icon. bounds: Frame [xmin, ymin, zmin, xmax, ymax, zmax], world space. A point is framed as a 1-unit cube around it (padded in the reply).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boundsNo
pane_nameNo
node_pathsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / bounds
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Bounds"
+}
    • addedInput schema / properties / node_paths
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Node Paths"
+}
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and adds meaningful behavioral detail: it explains how node_paths frames object types (null marker, camera/light icon) and how bounds handles point inputs (1-unit cube, padded in reply). It does not disclose side effects on selection or whether the view change is undoable, but for a viewport operation this is largely sufficient.

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 front-loaded with the tool's purpose, then uses a clean Args section to document parameters. Every sentence adds value, with no redundancy or filler.

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?

Given the low-risk viewport operation, no annotations, and no output schema, the description covers purpose and parameter semantics well. It could be slightly more complete by mentioning default behavior for pane_name (e.g., active pane) or clarifying the nature of the 'reply' referenced for padded bounds.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 does so thoroughly for all three parameters. It documents pane_name, provides detailed semantics for node_paths (world bounds, object-specific framing), and fully specifies the bounds format including edge-case behavior for a point.

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 clearly states the tool's action: framing geometry in the viewport, with modes for all geometry, specific nodes, or a box. It does not explicitly differentiate from the sibling 'frame_selection' tool, so it falls 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?

The description implies usage by describing what the tool does and the effects of its arguments, but it never states when to use this tool versus alternatives like 'frame_selection' or 'set_viewport_camera'. The context is clear but lacks explicit routing guidance.

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