Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_viewport_direction

Set the Houdini viewport to front, back, top, bottom, left, right, or perspective, or position the free view with rotation, pivot, and distance.

Instructions

Set the viewport to a standard viewing direction, or place the free view.

rotation/pivot/distance orbit the viewport's own (non-camera) view: rotation [rx, ry, rz] in degrees about the pivot, distance from it. The reply reads the view back. Looking through a camera, move the camera.

Args: direction: "front", "back", "top", "bottom", "left", "right", or "perspective". pane_name: Pane tab name. rotation: [rx, ry, rz] degrees for the free view. pivot: [x, y, z] the free view orbits. distance: Distance of the free view from its pivot along its view axis (the dolly); a sideways pan is not counted in it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pivotNo
distanceNo
rotationNo
directionNo
pane_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / direction / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / direction / default
      Added value: +null
    • removedInput schema / properties / direction / type
      Removed value: -"string"
    • addedInput schema / properties / distance
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Distance"
+}
    • addedInput schema / properties / pivot
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Pivot"
+}
    • addedInput schema / properties / rotation
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Rotation"
+}
    • removedInput schema / required
      Removed value: -[
-  "direction"
-]
  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, the description carries the full behavioral burden. It usefully discloses that rotation/pivot/distance operate on the viewport's own non-camera view, that distance is a dolly and excludes sideways pan, and that 'the reply reads the view back.' It stops short of stating side effects, whether the change persists, or permission requirements, leaving meaningful gaps for a mutation-style operation.

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 is front-loaded in the first sentence and details follow in a structured Args block. Some sentences are dense and slightly awkward ('distance from it', the parenthetical about the dolly), but there is little pure filler and the ordering is sensible.

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 5-parameter tool with 0% schema coverage, no annotations, and no output schema, the description covers the parameters and the return behavior ('the reply reads the view back') well enough to call it correctly. Minor gaps remain around defaults (all null) and persistence/side effects, but nothing critical is missing.

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 must compensate, and it largely does: it enumerates the valid direction values ('front', 'back', 'top', 'bottom', 'left', 'right', 'perspective'), clarifies pane_name, and explains rotation format ([rx, ry, rz] in degrees), pivot, and the dolly semantics of distance. This meaning is not present in the schema at all, adding substantial value.

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 opening sentence states a specific verb and resource ('Set the viewport') and distinguishes two operating modes: a standard viewing direction versus placing the free view. It does not name the sibling set_viewport_camera it implicitly contrasts with, but an agent can still tell what the tool does without opening the schema.

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?

Usage is implied rather than explicit: the agent learns that this tool sets standard directions or the free view, and 'Looking through a camera, move the camera' hints that camera-driven views are out of scope. However, it never names the alternative tool (set_viewport_camera) or states a clear when-to-use-this-vs-that condition.

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