Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_usd_composition

Retrieve the composition arcs for a USD prim by specifying the Houdini node and prim paths, so you can inspect how USD layers and references combine.

Instructions

Get composition arcs for a USD prim.

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_path": "<prim_path>"
    },
    "name": "get_usd_composition"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYes
prim_pathYes

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?

With no annotations supplied, the description carries the full behavioral burden. 'Get' weakly implies a read operation, but it says nothing about side effects, permissions, whether the stage must be open, what arc types are covered (references, payloads, inherits, specializes, variants), or what the response contains.

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 single sentence is front-loaded and free of redundancy, but it is underspecified rather than appropriately concise for a two-required-parameter tool with zero schema documentation. Nothing needs removing, but more needs adding.

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?

No annotations, no output schema, and 0% parameter description coverage leave the definition with substantial gaps. Given the domain complexity of USD composition arcs and the required node_path/prim_path pair, the description is too thin for an agent to invoke this tool confidently.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and both parameters are required. The description does not explain what node_path is versus prim_path, how they relate, or what format either expects, so it provides no compensation for the undocumented schema.

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 states a specific verb ('Get') and resource ('composition arcs') scoped to 'a USD prim', which distinguishes it from sibling prim-inspection tools like get_usd_prim or get_usd_world_transform. It is clear but does not explicitly differentiate itself from adjacent USD tools or clarify which arc types are returned.

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, no mention of prerequisites such as a loaded stage or valid node context, and no alternatives named. The phrase 'for a USD prim' implies context but does not tell the agent when this tool is the right choice versus get_usd_layers, get_usd_variants, or get_usd_prim.

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