UE5-MCP-Server

by hahatu112113

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

ue5_destroy_actor

Remove an actor from the current Unreal Engine 5 level using its object path.

Instructions

Removes an actor from the current level by its object path.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 18, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits beyond the basic action. It does not mention if the destruction is permanent, if references are updated, or any side effects. The only implied behavior is that it's destructive.

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 a single, concise sentence that conveys the essential purpose without any filler. It is front-loaded and efficient.

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?

For a simple tool with one parameter and no output schema, the description is adequate but could include additional context about the permanence of the action or any impact on the level. It meets the minimum requirements but is not enriched.

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 schema already describes the only parameter (actorPath) with full coverage. The description adds no additional meaning beyond restating how the actor is identified. Baseline score of 3 is appropriate.

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 action ('removes'), the resource ('actor'), the scope ('current level'), and the method ('by its object path'). It is specific and distinctive from sibling tools like ue5_spawn_actor or ue5_get_all_level_actors.

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?

The description provides no guidance on when to use this tool versus alternatives, such as when actors should be destroyed versus hidden or deactivated. No prerequisites or conditions are mentioned.

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