Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_viewport_direction

Sets a Houdini viewport pane to a standard viewing direction or positions the free view using pivot, rotation, and distance.

Instructions

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

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": "set_viewport_direction"
  }
}

Input Schema

NameRequiredDescriptionDefault
pivotNo
distanceNo
rotationNo
directionNo
pane_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden, but it does not say whether this mutates the scene, how pivot/distance/rotation interact with direction, whether pane_name scopes the change, or what happens if conflicting parameters are supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single short sentence with no wasted clauses, but it is under-specified rather than appropriately concise for a five-parameter tool.

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?

For a tool with five optional parameters, no annotations, no output schema, and no parameter descriptions, the one-sentence description leaves major gaps about parameter interactions, valid values, and the resulting viewport state.

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?

All five parameters have 0% schema description coverage, and the description only vaguely gestures at direction and free view. It does not explain the units or shape of pivot and rotation, what distance means, which direction strings are valid, or what pane_name selects.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb and resource ("Set the viewport") and mentions a standard viewing direction, but the phrase "place the free view" is vague jargon and does not clearly distinguish this from sibling tools such as set_viewport_camera or set_viewport_display.

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 guidance on when to use this instead of set_viewport_camera, set_viewport_display, or the other viewport setters, nor any prerequisites or conditions for choosing between a standard direction and the free view.

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