Skip to main content
Glama

unreal_get_game_state

Fetches Unreal Engine game state class details so you can inspect state definitions and properties during editor workflows.

Instructions

Get game state class 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_game_state"
  }
}

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?

With no annotations, the description carries the full disclosure burden and reveals almost nothing: it does not state whether this is a read-only query, whether it requires an active editor/PIE session or loaded world, or what happens if no game state exists. The existence of an output schema covers return shape, but not the operational preconditions an agent needs.

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?

One short sentence with no filler, so nothing is wasted, but the brevity reflects under-specification rather than efficiency. There is no front-loaded scope statement or qualifying clause.

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?

For a tool in a dense sibling family with an opaque required parameter, no annotations, and no output-schema-independent context, the description does far too little. The output schema covers return values, but purpose disambiguation and parameter meaning remain unaddressed.

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?

The single required parameter is named "params" with 0% schema description coverage, so neither the schema nor the description explains what it should contain or whether it can be omitted. The description offers no compensating detail, leaving the only required input entirely opaque.

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 and resource ("Get game state"), but appends "class info," which is ambiguous — it is unclear whether this returns the GameState class type, its properties, or the live instance data. Siblings like unreal_get_game_mode and unreal_get_game_instance are close enough that an agent cannot confidently choose this tool from the text alone.

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 guidance on when to use this versus unreal_get_game_mode, unreal_get_game_instance, or unreal_get_active_world. No prerequisites, no exclusions, no context about the caller's world or PIE session state is provided.

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