Skip to main content
Glama

unreal_manage_level_visibility

Show or hide a streaming level in Unreal Engine 5 to control which level content is visible through the editor bridge.

Instructions

Show/hide a streaming level.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 burden and discloses almost nothing. It does not state whether hiding unloads the streaming level or merely suppresses rendering, whether visibility persists across sessions, what permissions or editor state are required, or what happens to already-streamed data — all critical for a mutation that toggles world state.

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 sentence is waste-free and front-loaded, which is good, but its brevity reflects under-specification rather than economy. There is no structure to distinguish the two opposite behaviors it claims to support.

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?

The presence of an output schema means return values need not be documented, which partially offsets the thin description. Even so, a single-parameter mutation tool with an undocumented parameter blob and no annotations leaves the caller without the minimum information needed to invoke it correctly.

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?

Schema coverage is 0% and the single required 'params' property is an untyped, undocumented object. The description does not reveal what must be packed into it — level name/path, a boolean visible flag, or a load-state option — so the parameter is completely opaque from the definition alone.

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 verb-plus-resource pairing ('Show/hide a streaming level') is specific enough to identify the operation and its target, and the resource word 'level' does separate it from unreal_set_actor_visibility. However, 'show/hide' fuses two opposite operations into one phrase without saying whether a flag selects between them, so an agent cannot tell how the action resolves.

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 versus unreal_set_actor_visibility, unreal_open_level, or unreal_create_level. The 'streaming level' qualifier implies a scope but there is no stated condition, prerequisite, or exclusion, leaving the agent to infer the choice entirely.

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