UE5-MCP-Server

by hahatu112113

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

ue5_pilot_actor

Pilot an actor in the active editor viewport to view through a CameraActor or control its movement.

Instructions

Pilots an actor in the active editor viewport. Useful for seeing through a CameraActor.

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": {
      "actorPath": "<actorPath>"
    },
    "name": "ue5_pilot_actor"
  }
}

Input Schema

Name	Required	Description	Default
`actorPath`	Yes	The full object path of the actor to pilot.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 18, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral details. It fails to specify side effects such as viewport changes, requirement for an active viewport, or how to revert. The minimal description leaves significant behavioral gaps.

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

Conciseness5/5

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

The description is extremely concise at two sentences, with no filler. Every word serves a purpose, making it easy to parse quickly.

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

Completeness3/5

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

Given the simple nature of the tool (one parameter, no output schema), the description is adequate for basic understanding but omits essential behavioral context. It is minimally complete but not robust.

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

Parameters3/5

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

The only parameter 'actorPath' is fully described in the input schema (100% coverage). The description adds no extra semantic value beyond the schema, meeting the baseline for full coverage.

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

Purpose5/5

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

The description clearly states the tool pilots an actor in the active viewport and specifically notes its usefulness for seeing through a CameraActor. It distinguishes from the sibling ue5_eject_pilot by addressing a complementary action.

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

Usage Guidelines4/5

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

The description provides a use case ('useful for seeing through a CameraActor'), giving context for when to use. However, it lacks explicit guidance on when not to use or mention of the complementary tool ue5_eject_pilot for stopping piloting.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.