Skip to main content
Glama

unreal_create_sublevel

Create a streaming sublevel to organize large Unreal Engine 5 worlds and load level content dynamically without overloading the main level.

Instructions

Create a streaming sublevel.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and mostly drops it. Beyond the word 'streaming', it does not say where the sublevel is created, whether it is saved to disk, whether it attaches to a currently open level, or what side effects occur; only the fact that it is a creation/mutation operation is conveyed.

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

Conciseness3/5

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

One front-loaded sentence with no filler, so nothing is wasted. The terseness is not padding, but it leaves the sentence doing far less work than needed for a creation tool with an undefined parameter object.

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

Completeness2/5

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

The existence of an output schema relieves the description of explaining return values, but the empty 'params' schema plus absent annotations means the description is the only source of usage and behavior information, and it supplies almost none. For a mutation tool this is noticeably under-complete.

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 required parameter is an opaque object titled only 'Params' with 0% schema description coverage, and the description adds no meaning at all to it. There is no hint of what fields it expects (name, path, parent level, streaming method), so the agent cannot construct a valid call from either the schema or the description.

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

Purpose3/5

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

States a concrete verb+resource ('Create a streaming sublevel'), which is more specific than a bare name restatement. However, it gives no way to distinguish it from the sibling unreal_create_level or unreal_create_world_partition_info, and does not say what a 'streaming sublevel' means in this context (an asset? a level-streaming entry under an existing persistent level?).

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 prerequisite (e.g. must a persistent level already exist?), and no mention of alternatives such as unreal_create_level. The agent must infer everything about when this tool applies.

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