Skip to main content
Glama

unreal_create_world_partition_info

Inspect Unreal Engine 5 world partition information to review level streaming setup and data layer configuration before editing.

Instructions

Inspect world partition info when available.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden of disclosure and fails to say whether the operation is read-only or mutating, what permissions it needs, or what happens on unsupported maps. The word "Inspect" hints at a read, but the "create_" in the name directly undercuts that hint, leaving the behavior ambiguous.

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?

It is a single short sentence with no filler, so it is structurally clean. However, the brevity comes at the cost of substance rather than from efficient expression of a complete idea.

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?

An output schema exists, so return values are partly covered by structured data. Still, with one opaque parameter and no annotations, the description leaves the caller without enough to invoke the tool correctly or predict its effect.

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 a bare untyped object named "params" with 0% schema description coverage, and the description says nothing about what belongs inside it. There is no way for an agent to construct a valid argument from the definition alone.

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

Purpose2/5

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

The description says "Inspect world partition info when available," which names a resource but gives no detail about what world partition info means or what inspecting it yields. It also conflicts with the tool name's "create_" prefix, so an agent cannot tell whether this creates or reads state. That mismatch pushes it below the minimum-viable bar for purpose.

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 only conditional cue is "when available," which does not tell the agent how to determine availability or what to do when it is not. No sibling alternative (e.g., unreal_get_world_info) is named or excluded, even though several get_world tools exist in the catalog.

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