Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_usd_prim_specifier

DestructiveIdempotent

Change a USD prim's specifier to Def, Over, or Class at the current edit target, refusing unknown values before write.

Instructions

Change the specifier ("Def", "Over" or "Class") of an existing prim on a registered USD stage, at the current edit target. An unknown specifier is refused before anything is authored. specifier reports the one written, only when the write succeeded (set); a failed write fails the call. Not saved to disk.

Returns: { set: bool, specifier?: string, requested?: object }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prim_pathYesAbsolute SdfPath of an existing prim, e.g. "/World/Cube".
specifierYes"Def", "Over" or "Class", case-insensitive; anything else is refused.
stage_nameNoName the stage was registered under by create_usd_stage or open_usd_stage; a stage already in the USD cache also matches by the end of its root layer identifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • changedInput schema / properties / specifier / description
      Previous value: -"\"Def\", \"Over\" or \"Class\", case-insensitive; anything else is applied as \"Def\"."New value: +"\"Def\", \"Over\" or \"Class\", case-insensitive; anything else is refused."
  2. Changed3 schema fields changedv1.2.0
    • changedInput schema / properties / prim_path / description
      Previous value: -"Target prim path"New value: +"Absolute SdfPath of an existing prim, e.g. \"/World/Cube\"."
    • changedInput schema / properties / specifier / description
      Previous value: -"\"Def\" | \"Over\" | \"Class\""New value: +"\"Def\", \"Over\" or \"Class\", case-insensitive; anything else is applied as \"Def\"."
    • changedInput schema / properties / stage_name / description
      Previous value: -"Stage cache key"New value: +"Name the stage was registered under by create_usd_stage or open_usd_stage; a stage already in the USD cache also matches by the end of its root layer identifier."
  3. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing validation-before-authoring ('refused before anything is authored'), atomic write semantics ('specifier reports the one written, only when the write succeeded'), and persistence scope ('Not saved to disk'). These are meaningful traits the readOnly/destructive/idempotent hints do not convey, though permission requirements remain unstated.

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?

Front-loads the core action and keeps the behavioral caveats tight. The trailing 'Returns:' block is justified given there is no output schema, though its presence makes the whole slightly denser than a pure behavioral blurb.

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?

With no output schema, the description usefully sketches the return shape (set/specifier/requested) and the failure path. For a mutation tool whose annotations cover the safety profile, this is nearly complete; only permission/reversibility specifics are 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 coverage is 100%, so the schema already documents all three parameters including the specifier enum and case-insensitivity. The description restates the specifier values but adds no syntax or validation detail beyond the schema, so it lands at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb+resource: changing the specifier of an existing prim on a registered USD stage. The scope qualifier 'at the current edit target' and the enumeration of valid specifier values make the operation unambiguous relative to siblings like set_usd_prim_type or override_usd_prim.

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 qualifier 'existing prim' implies the tool is for already-authored prims rather than creation, which is useful context. However, it never explicitly names the alternatives (define_usd_prim, override_usd_prim) or states when to choose them, leaving routing to inference.

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