Skip to main content
Glama

set_prim_transform

Move, rotate, or resize a prim by setting its position, rotation, or scale relative to its parent; any omitted transform values remain unchanged.

Instructions

Set a prim's position, rotation or scale relative to its parent; any of the three left out keeps its value.

Use it to move, turn or size a prim; to aim the viewport camera, use set_camera, and to push a rigid body while physics runs, apply_force. Values are in the parent's space, not world space: get_prim_properties gives a prim's world position. It writes into the prim's own xform ops: the position into its translate op, the rotation into its rotate or orient ops in their kind, the scale into its scale op, adding an op it lacks; other ops, a pivot among them, stay. A part with no op of its own goes into the prim's matrix (xformOp:transform) when it has one, as imported assets often do. An error when the prim doesn't exist or can't be transformed, for an animated op, for ops a stronger layer holds, such as a Kit camera's, and for a rotation or scale on a matrix that can't be factored.

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>"
    },
    "name": "set_prim_transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoA uniform scale, or [sx, sy, sz]
positionNo[x, y, z] relative to the parent prim, in the stage's units (get_sim_state's meters_per_unit)
rotationNoEuler angles [rx, ry, rz] in degrees, or a quaternion [w, x, y, z]
prim_pathYesFull USD path of the prim, e.g. "/World/Robot"

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.3
    • changedInput schema / properties / position / description
      Previous value: -"[x, y, z] in the stage's units (usually metres)"New value: +"[x, y, z] relative to the parent prim, in the stage's units (get_sim_state's meters_per_unit)"
  2. First observedv0.2.2

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations, which only declare readOnly=false, destructive=false, openWorld=false. The description discloses exactly which xform ops get written (translate, rotate/orient in kind, scale), that missing ops are added, that untouched ops such as pivots are preserved, and the matrix fallback for imported assets. It also enumerates concrete error conditions (missing prim, animated op, stronger-layer override like a Kit camera, non-factorable matrix), which is unusually specific for a mutation tool.

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?

The core operation and the parent-space caveat are front-loaded in the first clause, then usage, then mechanism, then errors. The later sentences are long and densely packed with USD op vocabulary, but each carries distinct information; nothing is padding.

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 four-parameter mutation with full annotations and an output schema, this covers coordinate frame, op-level write behaviour, preservation of other ops, the matrix fallback, and failure modes. Return values need not be explained because an output schema exists, and the only remaining gap is minor granularity on some error cases.

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 baseline is 3; the description earns an extra point by explaining that any of the three omitted values 'keeps its value' rather than resetting to zero, and by insisting the values are in the parent's space, not world space. Those are semantic clarifications the null defaults in the schema do not convey on their own.

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 ('Set a prim's position, rotation or scale relative to its parent') and immediately clarifies the parent-space frame, which is the key distinguishing trait versus a world-space or camera tool. An agent can identify this apart from set_camera, apply_force, and get_prim_properties without opening any 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?

Explicitly says what the tool is for ('move, turn or size a prim') and routes two near-neighbours elsewhere: set_camera for aiming the viewport, apply_force for pushing rigid bodies under physics. It also names get_prim_properties as the way to read world position, which resolves the most likely confusion about coordinate frames.

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