Skip to main content
Glama

unreal_get_game_instance

Retrieves game instance class information from an Unreal Engine 5 project, enabling AI clients to inspect runtime game instance details through the editor bridge.

Instructions

Get game instance 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_instance"
  }
}

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 of behavioral disclosure, and it says nothing about whether the call is read-only, what permissions or PIE context it requires, or what happens if no game instance exists. Because an output schema exists, return-value detail is not strictly required, but the near-total absence of behavioral context for an unannotated tool leaves this at a 2.

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?

It is a single front-loaded sentence with zero waste, but for a tool with a wholly undocumented parameter the brevity crosses from concise into under-specified. The structure is fine; the sizing is too small for the gaps it leaves.

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 tool is conceptually simple and the presence of an output schema relieves the description of explaining return values, so it is close to callable. The unresolved gap is the opaque 'params' object and the missing behavioral context in the absence of annotations.

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', whose schema is an untyped object with 0% description coverage, and the description adds no information about what should go inside it. Since the schema is effectively silent, the description had an obligation to explain the parameter and does not.

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 verb ('Get') and a resource ('game instance class info'), which does distinguish it from siblings like unreal_get_game_mode and unreal_get_game_state. However, 'class info' is vague — it does not say whether it returns the class name, full reflection data, or a hierarchy, so an agent cannot confidently predict the payload.

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, and no routing to related tools such as unreal_get_game_mode or unreal_get_game_state. The agent must infer that this is a read-only introspection call from the name alone.

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