Skip to main content
Glama

unreal_get_actor_transform

Retrieve an actor's transform—location, rotation, and scale—from an Unreal Engine 5 project so you can inspect or use its placement data.

Instructions

Get actor transform.

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_get_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

D1.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about whether the actor must exist in the current world, what happens on an invalid handle, or whether the values are world-space or local. An output schema exists, which relieves it of explaining return fields, but the operational behavior remains undisclosed.

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

Conciseness2/5

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

The single sentence is short but under-specified rather than concise; it contains no information beyond the tool name. There is nothing unnecessary, but nothing that earns its place either.

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 output schema covers return values, but for a tool whose sole input is an opaque 'params' object and which has no annotations, the description leaves the caller without enough information to invoke it correctly. It should at minimum identify the actor-identification parameter and the transform components returned.

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?

There is a single required parameter 'params' with 0% schema description coverage and no structure, and the description adds no meaning about what to supply. With no parameter documentation anywhere, the agent has to guess how to identify the actor.

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

Purpose2/5

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

The description 'Get actor transform' essentially restates the tool name (unreal_get_actor_transform) with no added specificity. It does not clarify what 'transform' covers (location, rotation, scale), nor does it distinguish this from siblings like unreal_get_actor_details or unreal_get_actor_components.

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 use this versus unreal_get_actor_details or the individual getter siblings, and no prerequisites or exclusions are stated. The read-only nature of the operation can only be inferred from the verb 'Get' in the name.

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