Skip to main content
Glama

unreal_set_actor_location

Move an actor to specified coordinates in an Unreal Engine 5 level to adjust its placement via the editor bridge.

Instructions

Set actor location.

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_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are supplied, so the description must carry the full behavioral burden and it carries none: nothing about world vs relative coordinates, units, whether physics is affected, whether it teleports or sweeps, what permissions are needed, or what happens if the actor does not exist. Only the verb "set" implies a write, which is a bare minimum and leaves a mutation tool completely opaque.

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 sentence is short, but this is under-specification rather than conciseness; there is nothing front-loaded because there is nothing substantive. No sentence here earns its place beyond echoing the title.

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

Completeness1/5

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

An output schema exists, so return values need not be described, but for a mutation tool with a single fully undocumented opaque `params` object the description supplies no usable calling information. The complexity/coverage mismatch is severe.

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 one parameter, `params`, whose schema description coverage is 0% and whose type is untyped; the description adds no meaning at all. The single most important thing an agent needs — how to identify the actor and how to express the location vector — is documented nowhere.

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?

"Set actor location." only restates the tool name; it names no scope, coordinate space, or distinguishing behavior. It gives an agent no way to tell it apart from siblings such as unreal_set_actor_transform or unreal_set_viewport_location, and it reads as a tautology rather than a purpose statement.

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

Usage Guidelines1/5

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

The description contains no when-to-use guidance, no exclusions, and no mention of alternatives like unreal_set_actor_transform (which presumably also sets location alongside rotation/scale). An agent must infer everything from the name alone.

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