Skip to main content
Glama

unreal_set_actor_rotation

Set an actor's rotation in an Unreal Engine 5 level to align or orient it precisely.

Instructions

Set actor rotation.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing beyond the verb. It does not say whether the change is persisted, what coordinate space or unit (degrees vs. quaternion) applies, whether an actor must already be selected, or what happens if the actor is missing.

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?

Three words contain no wasted clauses, but this is under-specification rather than conciseness. There is no structure to front-load because there is essentially no content.

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 explained, but the sole input is completely opaque and the operation is a mutation on scene state. For a tool an agent must call with a correctly shaped rotation payload, the definition supplies none of the information required to do so.

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?

The schema has one required parameter literally named "params" with no type, no properties, and 0% description coverage. The description adds no meaning at all, so an agent cannot tell what shape of rotation value (Euler angle object, quaternion, axis-angle) must be supplied.

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?

States a concrete verb and resource ("Set actor rotation") so the agent knows it mutates an actor's orientation. It stops short of a 5 because it does not distinguish itself from close siblings like unreal_set_actor_transform (which also likely includes rotation) or unreal_set_viewport_rotation, leaving overlap unresolved.

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?

No when-to-use guidance, no prerequisites, no exclusions, and no pointer to alternatives. The agent must infer entirely on its own whether to use this versus unreal_set_actor_transform or unreal_set_viewport_rotation.

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