Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_usd_prims

Search USD prims by glob or substring pattern within a LOP node, optionally including instance proxy prototypes, to locate scene elements quickly.

Instructions

Search USD prims by path pattern.

Args: node_path: LOP node path. pattern: Glob pattern (supports *, **) or substring. traverse_instance_proxies: Search prims under instanceable prototypes too; the default walk never visits them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternYes
node_pathYes
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

B3.4/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 burden, and it does disclose one valuable non-obvious trait: the default walk never visits instanceable prototypes, so traverse_instance_proxies must be set to reach them. It does not state read-only nature, result size, ordering, or performance characteristics.

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

Conciseness5/5

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

One summary sentence followed by a compact Args block; every line adds information and the purpose is front-loaded. No padding or restated boilerplate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, annotations, or sibling differentiation, the description should ideally say what a match returns (prim paths? full paths?) and whether the search is scoped to the node's stage. It covers the parameters well but leaves the return shape and comparative positioning unspecified.

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: it maps node_path to "LOP node path", explains pattern accepts globs (*, **) or a substring, and clarifies the non-obvious semantics of traverse_instance_proxies. Only the exact pattern-matching precedence is left ambiguous.

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 first sentence gives a specific verb and resource ("Search USD prims") plus the mechanism (path pattern), which is clearer than the vague sibling tools. However, it never distinguishes itself from close siblings like list_usd_prims or get_usd_prim, so an agent must guess which one to pick.

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 explicit when-to-use guidance and no mention of alternatives such as list_usd_prims or get_usd_prim. The pattern syntax note hints at how to call it, but nothing tells the agent when this tool is the right choice over its siblings.

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