Skip to main content
Glama

unreal_execute_console_command

Execute advanced Unreal Engine editor console commands to automate editor tasks, adjust settings, or trigger workflows beyond standard project actions.

Instructions

Execute an editor console command (advanced).

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden and fails it. It does not say whether commands are read-only or destructive, whether they require special permissions, whether side effects persist (e.g., editor state, unsaved assets), or what happens on an invalid command.

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 sentence is front-loaded and free of filler, which is good. But the parenthetical '(advanced)' is low-information, and the extreme terseness edges into under-specification rather than true 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?

An output schema exists, so return values need not be explained. However, for a potentially destructive, free-form execution tool with an undocumented parameter and no annotations, the definition omits essential context: command syntax, scope of effect, and safety expectations.

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?

There is one required parameter, 'params', and the schema description coverage is 0%. The description adds nothing about its expected form (single command string, array, quoting rules) or how to pass arguments embedded in a console command.

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 states a concrete verb and resource: 'Execute an editor console command'. An agent can tell what action is performed. It does not, however, distinguish this from the sibling unreal_execute_editor_python or clarify what an 'editor console command' means in this environment.

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?

The parenthetical '(advanced)' hints at caution but gives no when-to-use, when-not-to-use, or alternative-tool guidance. Nothing tells the agent how this differs from the Python-execution sibling or when a dedicated tool is preferable.

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