Skip to main content
Glama

unreal_set_game_mode

Sets the default game mode class in an Unreal Engine 5 project, defining which gameplay rules apply when levels are played or tested.

Instructions

Set default game mode class.

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_set_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.8/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 and delivers almost nothing: it does not say whether the setting is persisted to project config, whether it takes effect immediately or on next play session, what permissions/preconditions are required, or whether it is reversible. Only the bare implication of mutation is conveyed.

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 sentence that is front-loaded and contains no filler. However, the brevity is under-specification rather than economy — the same length budget could have included the parameter's expected form.

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?

An output schema exists, so return values need not be explained, but for a mutation tool with zero annotation coverage and a completely opaque 'params' object, the description should explain what the payload must contain and how the setting behaves. Neither is present, so an agent cannot reliably invoke the tool from this definition.

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 literally named 'params' with 0% schema description coverage and no nested structure, so the schema explains nothing. The description's mention of 'game mode class' weakly hints the payload should reference a game mode class, but gives no key name, format, or how to specify it, leaving an agent unable to construct a valid call from the definition alone.

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?

The description gives a specific verb and resource ('Set default game mode class'), which cleanly names the operation and implicitly pairs with the read-side sibling unreal_get_game_mode. It stops short of explicitly differentiating itself from siblings or clarifying the 'default vs. active' nuance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the verb 'Set' — an agent can infer this is the write counterpart to unreal_get_game_mode. There is no statement of when to use it versus alternatives, no prerequisite that a game mode class must exist/be loaded, and no note about whether the change is editor-only or applied at runtime.

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