Retrieve an entity's world transform from an O3DE scene using its entity ID, providing position, rotation, and scale data for editor or automation workflows.
Get the world transform of an entity.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It communicates a read operation via 'Get', but it does not disclose details such as how hierarchy is resolved, failure modes, or whether the result is computed on demand. For a simple getter this is adequate but minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one short, front-loaded sentence with no filler. It states the action and the object of that action directly, which is appropriately concise for a single-parameter getter.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity, a required single entity_id parameter, and an available output schema, the description is nearly complete. It clearly identifies the target and what is returned; only format details and explicit alternative routing are left unstated.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage and the tool description adds only that the operation applies to 'an entity'. It does not explain accepted formats for entity_id (e.g., path, UUID, name), though the parameter is clearly the target entity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Get') and resource ('world transform of an entity'), making the tool's function unmistakable. It is clearly distinct from sibling tools like set_transform and set_parent, which mutate or relate entities.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when the caller needs an entity's world-space transform, but it does not explicitly name alternatives or state when not to use it. With only one sentence, the usage context is present but not elaborated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.