Skip to main content
Glama

unreal_get_world_info

Retrieve current world and level details from an Unreal Engine 5 project so you can inspect loaded levels and environment context before editing.

Instructions

Get world and level info.

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_get_world_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.4/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 behavioral burden, yet it says nothing beyond the name. "Get" weakly implies a read-only, non-destructive call, but there is no disclosure of permissions, editor/play-session requirements, side effects, or whether the level context must be open first.

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?

The single short sentence is front-loaded and wastes no words, but the brevity comes from under-specification rather than efficiency. There is no structure beyond a bare phrase.

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 need not be described, but the input side is opaque and there is no usage or behavioral context. For a tool whose only parameter is fully undocumented, the description leaves an agent unable to call it reliably.

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

Parameters2/5

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

One required `params` object exists with 0% schema description coverage, and the description adds no meaning about its shape or contents. With a single opaque parameter entirely undocumented in both schema and description, an agent has nothing to construct a valid call from.

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?

The description names a verb (Get) and a resource (world and level info), which is more than a tautology, but "info" is generic and conflates two scopes (world vs level) without saying what either contains. It also fails to distinguish this from siblings such as unreal_get_active_world or unreal_get_project_info, so an agent cannot tell which read tool answers which question.

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 or when-not-to-use guidance, no mention of prerequisites, and no routing to alternatives among the many unreal_get_* siblings. An agent must guess whether this or unreal_get_active_world returns the world it needs.

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