Skip to main content
Glama

set_transform

Updates an O3DE entity's world position, rotation, or scale while changing only the transform components you provide.

Instructions

Set the world transform of an entity (only provided components are changed).

rotation is an [x, y, z, w] quaternion and scale an [x, y, z] vector, the effective scale to end up with (each element in (0, 1000]). The call goes to the AiCompanion gem's native set_transform request (works in secure mode) and returns the updated entity's JSON, the same shape as get_entity. The gem refuses an unknown entity or out-of-bounds values, and that is returned as an error.

On gem API 0.5.0 and later (gem 0.6.0) the quaternion and the scale are sent as is. A non-uniform scale is applied through the engine's Non-uniform Scale component (each element at least 0.01); an O3DE Transform itself holds only a uniform scale. A later uniform scale sets that component back to 1. The reply carries scale (uniform), non_uniform_scale and effective_scale.

On older gems the quaternion is converted to XYZ Euler degrees, a rotation at a gimbal pole (pitch within 0.02 degrees of plus or minus 90) goes through editor Python instead, which prints Transform set for entity [<id>], and a non-uniform scale is refused with non_uniform_scale_unsupported. The legacy transport also uses the editor-Python path. An all-zero quaternion is rejected before any path.

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": {
      "entity_id": "<entity_id>"
    },
    "name": "set_transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNo
positionNo
rotationNo
entity_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly: it discloses the quaternion/scale formats and bounds, error behavior (refuses unknown entities or out-of-bounds values), version-dependent behavior across gem API levels, gimbal-pole fallback via editor Python, non-uniform scale handling, and all-zero quaternion rejection. This is exceptionally rich behavioral context.

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 purpose is front-loaded in the first sentence, and the dense paragraphs that follow earn their place by covering version-specific and error-path behavior that an agent would otherwise get wrong. Slightly verbose but justified by genuine complexity.

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?

The output schema exists and the description still notes the return shape ('the updated entity's JSON, the same shape as get_entity'), plus error semantics. For a mutation tool with version differences and no annotations, nothing essential is missing.

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 0%, so the description must compensate, and it defines rotation as an [x,y,z,w] quaternion and scale as an [x,y,z] vector with elements in (0,1000]. Position and entity_id receive no such treatment, leaving a minor gap, but the two most error-prone parameters are well documented.

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 the world transform of an entity') and adds the partial-update scope ('only provided components are changed'). An agent can distinguish this from get_transform or set_parent 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 Guidelines3/5

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

Usage is implied through the semantics of a transform mutation and the partial-update note, but there is no explicit when-to-use or when-not-to-use guidance, and no naming of sibling alternatives such as get_transform or set_parent. The agent must infer routing.

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