Skip to main content
Glama

set_actor_transform

DestructiveIdempotent

Move, rotate, or scale one Unreal actor, writing its transform and returning the re-read values. Supports editor/PIE worlds, undo, and reliable saving from Python.

Instructions

Move, rotate and/or scale ONE actor (omitted components are left as they are) and return the actor's re-read transform plus the identity of the world that was written. Undoable, and it calls Modify() first -- which matters, because moving an actor from Python does NOT dirty its OFPA package and then save_level reports success while writing nothing. Takes a world selector, so it also reaches a LIVE PIE pawn (an editor-only lookup would answer "Actor not found" for an actor that exists in another world). Use batch_set_actor_transform for many actors, place_actor_on_terrain to drop one onto the landscape.

Returns: { actor JSON via DescribeActorObject, transform RE-READ off the actor after the write }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesActor's internal name (GetName) or editor label (GetActorLabel), case-insensitive whole-string match.
scaleNoOptional new WORLD scale, ARRAY form only: [x, y, z]. A malformed value silently becomes 0,0,0 and the actor disappears.
worldNoOptional: "editor" (default) | "pie" | "server" | "client" | "pie:N". In co-op the authoritative pawn lives on the server, and a move written to the client world will be corrected by replication.
locationNoOptional new WORLD location, ARRAY form only: [x, y, z]. Absolute, not a delta; an object or a shorter array is silently read as the origin, which teleports the actor to 0,0,0.
rotationNoOptional new WORLD rotation as the array [pitch, yaw, roll] -- note index 2 is ROLL, not yaw -- or, unambiguously, the object {"pitch":..,"yaw":..,"roll":..}, which is the recommended form.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations: undoable, calls Modify() first, and it explains the OFPA dirtying failure mode where save_level reports success while writing nothing — a genuinely non-obvious mutation hazard. It also discloses replication correction on client worlds. The only deduction is that it does not state the permission/authority requirements for writing to server vs editor worlds.

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 the core action and scoped efficiently in the first clause. The middle clause about Modify()/OFPA is dense and dash-heavy, but each sentence carries non-redundant information; nothing is padding.

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?

For a destructive, idempotent mutation with annotations covering the safety profile and no output schema, the description supplies the return shape (re-read transform + world identity), the undo semantics, the Modify() prerequisite, and the multi-world caveat. Nothing an agent needs to call it correctly is missing.

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% and the schema already carries the key param warnings (scale array-only, malformed value becomes 0,0,0; location is absolute not delta; rotation index 2 is ROLL). The description adds a little on the `world` selector's runtime significance, but mostly restates what the schema documents, so 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 triad (move, rotate, scale) operating on a precisely scoped resource (ONE actor, omitted components untouched) plus the return contract. It explicitly differentiates from siblings batch_set_actor_transform and place_actor_on_terrain, so an agent can pick correctly without opening another 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?

Names the two nearest alternatives and the condition selecting each ('for many actors', 'to drop one onto the landscape'), and explains when the `world` selector is required (a LIVE PIE pawn that an editor-only lookup would miss). This is explicit routing, not implied usage.

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