Skip to main content
Glama

unreal_set_actor_mobility

Change an actor's mobility setting in Unreal Engine 5 to control whether it is static, stationary, or movable, enabling correct lighting and physics behavior for level actors.

Instructions

Set actor mobility.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

With no annotations supplied, the description carries the full behavioral burden and delivers essentially nothing. It does not state the valid mobility values, whether the change is persisted, what happens to physics or existing simulation state, or what permissions/context are required for a mutation operation.

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?

It is short and front-loaded, but the brevity reflects under-specification rather than efficiency. A single sentence that duplicates the tool name earns no place in the definition.

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?

For a mutation tool with an opaque untyped parameter object, no parameter documentation, and no annotations, the definition supplies none of the information an agent needs to invoke it correctly. The presence of an output schema only excuses the absence of return-value documentation, not the missing input guidance.

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 single parameter is a generic untyped 'params' object with 0% schema description coverage, and the description says nothing about what should go inside it. An agent cannot determine the expected shape or the allowed mobility values from either source.

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 mobility" restates the tool name almost verbatim, adding no information beyond the verb+resource already visible in the identifier. It never explains what 'mobility' means in Unreal (e.g. static/stationary/movable) or what effect setting it has, and offers nothing to distinguish it from siblings such as unreal_set_actor_transform.

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 when-to-use guidance, no prerequisites, and no mention of alternatives or when the tool should not be used. The agent must infer entirely from the name that this changes an actor's mobility mode rather than its transform.

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