UE5-MCP-Server

by hahatu112113

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

ue5_new_level

Create and open a new empty level in Unreal Engine 5 by specifying the asset path.

Instructions

Creates and opens a new empty level at the given asset 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": {
      "assetPath": "<assetPath>"
    },
    "name": "ue5_new_level"
  }
}

Input Schema

Name	Required	Description	Default
`assetPath`	Yes	The asset path for the new level (e.g., '/Game/Maps/MyNewLevel').

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, so the description must carry full behavioral burden. It does not disclose whether the operation overwrites an existing asset, requires specific permissions, or what happens if the path is invalid. Missing key behavioral traits.

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 sentence that conveys the essential purpose without any extraneous text. 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?

Given the simplicity of one parameter and no output schema, the description states the basic action. However, it lacks behavioral and contextual details needed for safe and effective use, such as overwrite behavior and prerequisites.

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?

Schema coverage is 100% with the assetPath parameter already described with an example. The tool description does not add any additional meaning beyond what the schema provides, so a 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 it creates and opens a new empty level at a given asset path, using specific verbs and resource. It distinguishes itself from siblings like ue5_save_level which saves an existing level, or ue5_delete_asset which deletes.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., project must be open, path must not exist) or exclusions such as overwriting behavior. Usage context is unclear.

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