Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_usd_prim_stats

Count USD prims by type under a root path in a Houdini LOP node, optionally traversing instance proxies to include prototype contents.

Instructions

Get prim counts by USD type under a root path.

Instanced geometry counts once per prototype, not per instance: instanceable_prims says how many prims were counted without their contents, and traverse_instance_proxies counts what is under them.

Args: node_path: LOP node path. prim_path: Root prim path to gather stats from. traverse_instance_proxies: Count prims under instanceable prototypes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_pathYes
prim_pathNo/
traverse_instance_proxiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv2.21.0
    • addedInput schema / properties / traverse_instance_proxies
      Added value: +{
+  "default": false,
+  "title": "Traverse Instance Proxies",
+  "type": "boolean"
+}
  3. First observedv0.1.0

TDQS

A3.6/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 behavior burden and does well: it explains that instanced geometry is counted once per prototype rather than per instance, and that instanceable_prims and traverse_instance_proxies control what gets counted. It only omits explicit read-only framing, which is strongly implied by 'get'.

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?

Purpose is front-loaded in one sentence, the instancing caveat follows, and the Args block is compact and scannable. Minor redundancy between the body text and the Args entry for traverse_instance_proxies, but nothing wasteful.

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?

No output schema exists, yet the description implies the return shape ('prim counts by USD type') and names a concrete returned field (instanceable_prims). For a 3-param read tool with no annotations, that is close to complete, with only the exact stats payload left implicit.

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 description coverage is 0%, so the description must compensate, and it does: node_path is identified as a LOP node path, prim_path as the root prim to gather from, and traverse_instance_proxies as counting under instanceable prototypes. This meaningfully exceeds the bare string/boolean type declarations in the 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?

States a specific verb (get) and resource (USD prim stats) with scope (counts by type under a root path), which clearly separates it from list_usd_prims and get_usd_prim. It does not explicitly name a sibling to distinguish from, so it falls just 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to reach for this tool instead of the many sibling prim-inspection tools (get_usd_prim, list_usd_prims, get_attrib_stats) and offers no prerequisites or exclusions. The instancing note helps interpret a result but is not usage routing.

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