Skip to main content
Glama

unreal_ping

Check whether the Unreal Editor bridge is reachable and responding before running inspect or edit operations on a project.

Instructions

Ping the Unreal Editor bridge.

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

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 burden, and it discloses almost nothing: not what a success versus failure looks like, not timeout behavior, not whether the call has side effects. The presence of an output schema offsets some of this, but the operational characteristics of a connectivity probe remain undocumented.

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 free of filler, which suits a trivial tool. However, brevity here shades into under-specification rather than disciplined conciseness.

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 relieves the description of explaining return values, but for a tool with a required undocumented parameter and zero annotation coverage, the definition leaves too much for the agent to guess. It should at minimum state what the required parameter is for and what the tool confirms.

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 schema declares a single required parameter named "params" with no type and no description (0% coverage), and the description says nothing about it. A ping conceptually needs no arguments, so the mandatory opaque "params" wrapper is left entirely unexplained and the agent has no way to know what to supply.

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

Purpose4/5

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

"Ping the Unreal Editor bridge" names a specific verb and target resource, and it is unmistakably distinct from the sibling creation/analysis tools. It stops short of saying explicitly that this is a connectivity/health check, but the intent is recoverable from standard usage of "ping".

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 mention of prerequisites (e.g. is the editor/bridge running?), and no comparison to alternatives. An agent must infer that this is a pre-flight connectivity check before invoking the many mutation tools.

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