Skip to main content
Glama

unreal_get_game_mode

Retrieves a project's default game mode, helping AI clients inspect Unreal Engine 5 gameplay settings before editing levels or actors.

Instructions

Get project/default game mode.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/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 disclosure burden, yet it says nothing about whether the call is read-only in practice, what happens with no project open, or what form the returned game mode takes. With an output schema present, some of the return-value burden is lifted, but the operational context is still absent.

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 short phrase with no filler, so nothing is wasted, but it is under-specified rather than genuinely concise. The key noun phrase is front-loaded, which is the one structural strength.

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, but for a one-parameter tool with an entirely undocumented 'params' object and an ambiguous scope ('project/default'), the description does not supply enough for reliable invocation. It should at least say what 'params' accepts and whether this reads the project default or the active world's override.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single 'params' object with no type and 0% schema description coverage, so the schema explains nothing. The description likewise adds no meaning about what belongs in 'params', leaving the agent to infer it, though the one-parameter surface limits the damage.

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 verb 'Get' plus resource 'project/default game mode' gives a rough idea, but the slash construction leaves it ambiguous whether this returns the project setting, the world default, or both. It also never distinguishes itself from the sibling unreal_set_game_mode, so an agent must guess which side of the get/set pair 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 statement of when to call this versus alternatives, no precondition such as requiring an open level or editor session, and no mention of the paired set tool. The agent gets no routing guidance at all.

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