Skip to main content
Glama

unreal_set_actor_transform

Set an Unreal Engine actor's location, rotation, and scale to position, orient, and size it within a level.

Instructions

Set actor location/rotation/scale.

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": {
      "params": "<params>"
    },
    "name": "unreal_set_actor_transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire burden, and it discloses nothing beyond the mutation itself. It does not say whether unspecified components are preserved or reset, whether the move is a teleport versus a swept move, whether coordinates are world or local space, or what permissions/actor state are required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no filler, so there is nothing to trim. The terseness is under-specification rather than verbosity, which limits the score.

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

Completeness2/5

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

The presence of an output schema relieves the description of explaining return values, but for a mutation tool with zero annotation coverage and a completely undocumented parameter object, the definition is not complete enough to invoke reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter is an opaque 'params' object with no documented shape or required fields. The description does not compensate at all, giving no indication of how location, rotation and scale values are packaged.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Set) and the three transform components (location/rotation/scale), which is clear enough for an agent to know what the tool mutates. It stops short of distinguishing itself from the sibling tools unreal_set_actor_location, unreal_set_actor_rotation and unreal_set_actor_scale, so the boundary is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to prefer this combined transform setter over the per-component siblings, nor any prerequisite or context requirement. An agent facing five similar setters must guess whether this overwrites all three components at once.

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