Skip to main content
Glama

unreal_get_status

Retrieve bridge and editor connection status to confirm whether an AI client can reach the Unreal Engine Editor before inspecting or editing project content.

Instructions

Get bridge and editor connection 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_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 provided, so the description carries the full behavioral burden, yet it only recites what the name already implies. It does not state whether the call fails or returns a disconnected state when the bridge is down, whether it is safe/cheap to poll, or what connection dimensions are reported; an output schema exists but that covers only the success shape, not failure or cost behavior.

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

Conciseness4/5

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

One short sentence, front-loaded with the resource, with no filler. It is efficient, though the brevity is achieved partly by omitting information the call requires.

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 explained, which keeps the description from being badly incomplete. Still, a tool with a required undocumented 'params' argument and a sibling overlap needs more than one sentence to be callable with confidence.

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 'params' has 0% schema description coverage and an untyped body, and the description says nothing about its contents. With zero compensating information, the agent has no way to know what to supply for the required argument.

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 supplies a specific verb and resource (get bridge and editor connection status), which is more than a tautology of the name. However, it overlaps heavily with the sibling unreal_get_editor_status, and it never clarifies whether this tool reports transport-level bridge health, editor play/compile state, or both, so an agent cannot cleanly pick between the two.

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 exclusion, and no mention of the near-identical sibling unreal_get_editor_status. The agent must infer that this is a pre-flight connectivity check rather than a per-editor status query.

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