Skip to main content
Glama

compare_prims

Compare two prims or two variants of one prim side by side to see mesh, face, vertex, triangle, bounds, and material differences, including B minus A and face-change percentage.

Instructions

Compare two prims, or two variants of one prim, side by side: mesh, face, vertex and triangle counts, world bounds and bound materials, with B minus A, and the change in faces as a percentage when A has faces.

Two modes:

  1. Two prims: prim_path_a and prim_path_b.

  2. Two variants: prim_path, variant_set, variant_a and variant_b; this mode wins when all four are given.

Variant mode switches to each variant in turn in Kit's session layer, then puts that layer back exactly as it was, so no file and no selection changes. An unknown variant set or variant is refused, listing those there, and so is a prim inside an instance, naming the instance. For one prim's counts, use get_mesh_stats.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compare_prims"
  }
}

Input Schema

NameRequiredDescriptionDefault
prim_pathNoTwo variants: the prim that has them
variant_aNoTwo variants: the first
variant_bNoTwo variants: the second
prim_path_aNoTwo prims: the first
prim_path_bNoTwo prims: the second
variant_setNoTwo variants: their variant set

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.6/5.0
Behavior4/5

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

Goes well past the annotations by disclosing that variant mode temporarily switches variants in Kit's session layer and then restores the layer exactly, with no file or selection changes — consistent with destructiveHint=false and readOnlyHint=false. It also documents refusal behavior (unknown variant set/variant listed back; prim inside an instance refused and the instance named), which annotations cannot convey. It does not cover cost or side effects on concurrent session state, so it falls just short of the top.

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-loaded with purpose and output fields, then cleanly segmented into numbered modes, then caveats. Dense but nearly every clause carries information; the session-layer restoration sentence is slightly long but justifies itself as the only statement that this call does not leave side effects.

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

Completeness5/5

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

An output schema exists, so return values need not be described, and the description instead covers the things an agent must know to call correctly: mode selection, precedence, restoration of session state, and the two refusal conditions. Nothing material is missing for a comparison tool of this complexity.

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 coverage is 100%, so the per-parameter meanings are already given and the baseline is 3. The description adds real value on top by grouping the six flat parameters into two mutually exclusive modes and stating a precedence rule (all four variant params present means variant mode wins), which the schema does not express.

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 (compare) plus the two resources it operates on (two prims, or two variants of one prim) and enumerates the compared metrics: mesh, face, vertex and triangle counts, world bounds, bound materials, B minus A deltas. It explicitly routes single-prim counting to get_mesh_stats, so an agent can separate it from that sibling 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 Guidelines5/5

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

Gives two numbered modes with the exact parameter sets that select each, and resolves the ambiguity an agent would hit: variant mode wins when all four variant parameters are given. It also names the alternative (get_mesh_stats) for the one-prim case.

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