Skip to main content
Glama

unreal_get_editor_status

Retrieve Unreal Editor play/PIE and selection status to verify whether simulation is running and what is selected before editing or automation.

Instructions

Get editor play/pie and selection status.

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

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. It implies a read ('Get') but does not say whether the editor must be in a PIE session, whether selection is returned as actor references or names, or what happens when no editor is running. Only the existence of an output schema keeps this above the minimum.

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 sentence is front-loaded and wastes no words, but the brevity comes at the cost of under-specification; the unexplained 'pie' abbreviation and the missing argument guidance mean the terseness is not purely a virtue here.

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 output schema covers return values, so the description need not explain them. But a required undocumented 'params' object and no statement of the editor-state preconditions leave an agent unable to call this confidently in one shot.

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?

There is one required parameter ('params') with 0% schema description coverage and no type detail in the schema. The description adds nothing about what to pass — whether it can be omitted, whether it carries filters, or what shape it takes. For a required free-form object, this is a real documentation gap.

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 specific verb ('Get') and resource ('editor') and enumerates the two facets returned: play/PIE state and selection. That is more than a restatement of the name. However, 'pie' is unexplained jargon and nothing distinguishes it from siblings like unreal_get_status or unreal_get_active_world, so the agent must guess which status tool to use.

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 at all — no statement of prerequisites (e.g. editor must be running), no conditions favoring this over unreal_get_status or unreal_job_status, and no exclusions. The agent is left to infer usage entirely from the name.

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