Skip to main content
Glama

unreal_execute_editor_python

Run Python scripts inside Unreal Editor to automate project tasks, inspect assets, and trigger editor workflows through advanced mode.

Instructions

Execute Unreal Editor Python (advanced 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_execute_editor_python"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/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 burden of behavioral disclosure. It does not state that arbitrary user code executes with editor-side effects, whether the editor must be running, whether the operation is destructive or reversible, or what any safety/permission constraints are. Naming it "Python execution" implies code execution, but nothing beyond that is disclosed.

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 sentence with no filler, so nothing is wasted, but it is under-specified rather than concise. The unexplained "(advanced mode)" parenthetical occupies the only detail slot without conveying information.

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 described. But for an arbitrary-code-execution tool with no annotations and a completely opaque input object, the definition leaves the agent unable to call it correctly or anticipate its effects.

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?

The single required parameter "params" has 0% schema description coverage and is defined as a bare untyped object. The description adds nothing about what "params" must contain (a script string? a dict of arguments?), so an agent has no basis for constructing a valid call.

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 and resource ("Execute Unreal Editor Python"), so the agent knows it runs Python inside the editor. However, "advanced mode" is undefined and does nothing to distinguish this from the sibling unreal_execute_console_command, leaving the agent to guess what 'advanced' means.

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 exclusion of alternatives, and no mention of the console-command sibling that likely serves a similar purpose. The only hint is the unexplained parenthetical "(advanced mode)", which does not tell an agent when this tool is the right choice.

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