Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_usd_prim

Retrieve detailed USD prim information. Large array attributes are summarized to avoid huge outputs; use full=True for complete data.

Instructions

Get detailed info about a USD prim.

Array attributes longer than 16 elements (points, faceVertexIndices, primvars:st, ...) come back as a summary: size, element_type, the first 8 as head, and min/max for numeric data. That is what a mesh question needs; the full arrays of a building ran to 6.6 million characters. Pass full=True for every element, or read one array in windows with get_usd_attribute(offset=, limit=).

Args: node_path: LOP node path. prim_path: USD prim path. full: Return array attributes in full instead of summarised.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNo
node_pathYes
prim_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.18.0
    • addedInput schema / properties / full
      Added value: +{
+  "default": false,
+  "title": "Full",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the summarization behavior for large arrays, including size, element_type, head, and min/max, and provides a rationale (6.6 million characters). It does not cover error conditions or the full return format, but the disclosed behavior is significant and goes beyond a generic 'get info' statement.

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?

The description is front-loaded with the purpose, then explains the key behavioral nuance with a concrete example, and ends with a clear parameter list. Every sentence serves a purpose, and the structure is easy to scan.

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?

The description thoroughly covers array behavior and parameter semantics, but with no output schema and no annotations, it leaves the overall return structure vague ('detailed info'). It does not specify what non-array fields are returned or how errors are handled, which an agent might need to reliably parse the result.

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. It explains each parameter concisely: node_path as LOP node path, prim_path as USD prim path, and full as a toggle for full vs summarized arrays. This adds meaning beyond the bare schema property names and defaults, though 'LOP node path' and 'USD prim path' assume domain knowledge.

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 'Get detailed info about a USD prim' clearly states the verb and resource, and the additional details about array summarization differentiate it from generic listing tools. However, it does not explicitly distinguish it from siblings like get_usd_prim_stats or get_prim_intrinsics, though the name and explanation make the purpose clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives concrete usage context: 'That is what a mesh question needs' and directs users to get_usd_attribute for reading arrays in windows. It does not explicitly mention when to prefer other sibling tools for stats or intrinsic data, but the guidance provided is specific and actionable.

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