Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

list_usd_prim_attributes

Read-onlyIdempotent

List every attribute of a USD prim on an open stage, including type, value, authored status, and time samples, without changing the stage.

Instructions

List every attribute of a prim on an open USD stage without changing it. Returns count and attributes [{name, type_name, cpp_type, has_value, has_authored_value, time_sample_count}]; has_value also counts fallback values, has_authored_value only authored opinions.

Returns: { prim_path: string, attributes: [{name, type_name, cpp_type, has_value, has_authored_value, time_sample_count}], count: int }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prim_pathYesAbsolute SdfPath of an existing prim on that stage, e.g. "/World/Cube".
stage_nameYesName the stage was registered under by open_usd_stage (default the file basename) or create_usd_stage (default "Untitled").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / prim_path / description
      Previous value: -"Target prim path"New value: +"Absolute SdfPath of an existing prim on that stage, e.g. \"/World/Cube\"."
    • changedInput schema / properties / stage_name / description
      Previous value: -"Stage cache key"New value: +"Name the stage was registered under by open_usd_stage (default the file basename) or create_usd_stage (default \"Untitled\")."
  2. First observedv1.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so 'without changing it' is redundant, but the description adds real value by explaining that has_value counts fallback values while has_authored_value counts only authored opinions. That distinction is a genuine behavioral disclosure not present in the annotations.

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?

Front-loaded with the purpose, which is good, but the attribute field list and return shape are effectively stated twice (the inline array and the 'Returns:' block), creating redundancy. Moderately efficient but not tight.

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?

For a read-only listing tool with full schema coverage and clear annotations, the description supplies the return shape and the authored-vs-fallback value semantics that an agent needs. It is complete enough that no critical calling detail is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so both stage_name and prim_path are already documented in the schema, and the description adds no additional parameter semantics. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 (List) and resource (every attribute of a prim) scoped to an open USD stage, which reads clearly and distinguishes it from siblings like list_usd_prims. It stops short of explicitly naming the sibling it is not, so it is a strong 4 rather than 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 Guidelines3/5

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

The phrase 'on an open USD stage' implies the prerequisite that a stage must already be open, but there is no explicit when-to-use or when-to-use-alternative guidance against list_usd_prims or get_usd_prim_info. Usage is only implied.

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