Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_usd_world_transform

Retrieves world transforms for specified USD primitives at one or more frames in Houdini, enabling accurate spatial queries and scene validation.

Instructions

World transform of USD prims at one or more frames.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "node_path": "<node_path>",
      "prim_paths": "<prim_paths>"
    },
    "name": "get_usd_world_transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
framesNo
node_pathYes
prim_pathsYes

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 provided, so the description carries the full behavioral burden and delivers almost nothing. It does not state what a null 'frames' means (current frame?), whether results are world-space matrices per frame, how missing or invalid prim paths are handled, or whether node_path must be the stage-holding node.

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?

It is a single tight sentence with the key scope ('one or more frames') front-loaded and no wasted wording. Brevity here reflects under-specification rather than good editing, but the structure itself is clean.

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 no annotations, no output schema, two required parameters and zero schema documentation, the description is far too thin. Critical details — the return type (per-frame matrices?), frame defaulting behavior, and the role of node_path — are all absent.

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?

Schema description coverage is 0%, so the description must compensate, and it only loosely gestures at two of three parameters ('prims' and 'frames'). The required 'node_path' parameter is entirely unexplained, leaving no way to know which node the prim paths are resolved against or what format the paths take.

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 names a specific resource ('world transform of USD prims') and a temporal scope ('one or more frames'), so an agent can infer it is a read of transform data. However, it is a bare noun phrase with no verb and gives no basis for distinguishing it from siblings such as get_usd_prim or get_bounding_box, which may also report transform/spatial data.

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 when-to-use guidance at all: nothing says whether this is the right tool for a single prim versus a batch, what to do if only one frame is needed, or how it relates to set_object_transform for the write side. The agent must infer usage entirely from the tool name.

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