unreal-engine-mcp

by harn3ss

Overview Schema Source Related Servers Discussions Admin

Python

Local

new_level

Create a new empty level asset in Unreal Engine at a specified content path.

Instructions

Create a new empty level asset at a content path (e.g. '/Game/Maps/Test').

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": {
      "asset_path": "<asset_path>"
    },
    "name": "new_level"
  }
}

Input Schema

Name	Required	Description	Default
`asset_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 13, 2026

TDQS

A3.6/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 traits. It does not mention side effects (e.g., overwrite behavior), required permissions, or any state changes beyond creation. The output schema is not described, leaving the return value unspecified.

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, front-loaded sentence that efficiently conveys the core functionality. No redundant or missing information for a simple create operation.

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

Completeness4/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 an output schema (not shown), the description is mostly complete. It could be enhanced by noting whether the path must be unique or if the tool returns the created asset, but the output schema likely covers return values.

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

Parameters4/5

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

The single parameter 'asset_path' has no schema description (0% coverage). The description adds value by specifying the expected path format with an example ('/Game/Maps/Test'), which is essential for correct invocation. This partially compensates for the lack of schema documentation.

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 ('create'), the resource ('new empty level asset'), and the required input ('content path') with an example format. This distinguishes it from sibling tools like create_blueprint or create_material which create different asset types.

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 (e.g., load_level for existing levels). It does not specify prerequisites, such as whether the parent directory must exist, or what happens if the asset path already exists.

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