Skip to main content
Glama

create_variant_structure

Add empty variants to a USD prim and select a default, ready to author and switch between without replacing existing sets.

Instructions

Add a variant set of empty variants to a prim and select one, ready to fill and to switch between with set_variant_selection.

A set or variant that already exists is kept and added to, never replaced. The variants hold nothing until you author into them, with execute_script. An error when the prim doesn't exist.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prim_path": "<prim_path>",
      "variant_set_name": "<variant_set_name>",
      "variant_names": "<variant_names>"
    },
    "name": "create_variant_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
prim_pathYesThe prim to add the variant set to
variant_namesYesThe variants to create, e.g. ["focused", "shell"]
default_variantNoThe variant to select; the first of variant_names when empty or not among them
variant_set_nameYesThe new variant set's name, e.g. "model"

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.3
    • changedInput schema / properties / default_variant / description
      Previous value: -"The variant selected at first; the first when empty"New value: +"The variant to select; the first of variant_names when empty or not among them"
  2. First observedv0.2.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, closed-world. The description adds genuinely new behavior beyond that: merge semantics ('kept and added to, never replaced'), that variants start empty, and the error condition when the prim doesn't exist. It doesn't cover return shape, but an output schema exists so that's acceptable.

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?

Three short paragraphs, front-loaded with the action, then merge semantics, then the authoring pointer. Minor inefficiency in the fragment 'An error when the prim doesn't exist.', but nothing is padded.

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 mutation tool with annotations and an output schema, the description covers creation, selection, merge behavior, follow-up authoring, and the failure mode. The only gap is what the returned structure contains, which the output schema presumably covers.

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 all four parameters are documented in the schema, including the default_variant fallback to the first entry. The description reinforces that one variant is selected at creation but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 specific verb and resource: 'Add a variant set of empty variants to a prim and select one'. It also names the complementary sibling, set_variant_selection, so an agent can distinguish creation from switching without opening either schema.

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?

Gives clear operating context: variants are empty until authored via execute_script, and existing sets are added to rather than replaced. It stops short of an explicit 'do not use this when...' exclusion, but the creation-vs-switching split with set_variant_selection is implied well enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.