Skip to main content
Glama
miracle1814

ue5-automation

by miracle1814
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ue5_execute_command

Execute any whitelisted bridge command by name to access advanced Unreal Editor operations, such as materials and UMG widgets, when no dedicated tool exists.

Instructions

Escape hatch: run any whitelisted bridge command by name — the full 101-command surface, including capabilities without a dedicated tool (materials, UMG widgets, and other advanced operations). Prefer the dedicated tool whenever one exists for the operation; this generic entry point is the last resort and its arguments are less validated. Use ue5_tool_search{query} to find exact command names and their params. 101 commands cover materials/UMG/tasks/undo/PIE/logs/batch. Unknown command → fail-loud拒绝。| 白名单透传；命令名用 ue5_tool_search 查。

Input Schema

NameRequiredDescriptionDefault
paramsNoCommand arguments object | 该命令的入参对象
commandYesWhitelisted command name (see description list) | 白名单命令名（见描述中的全量清单）
session_idNoOptional session/owner for asset lock checks | 可选：会话标识（写命令做协作锁检查）
idempotency_keyNoOptional idempotency key; a repeated key within 10 min replays the prior success | 可选：幂等键（10 分钟内重放上次成功结果）

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv6.5.4
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "description": "Optional idempotency key; a repeated key within 10 min replays the prior success | 可选：幂等键（10 分钟内重放上次成功结果）",
+  "type": "string"
+}
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Optional session/owner for asset lock checks | 可选：会话标识（写命令做协作锁检查）",
+  "type": "string"
+}
  2. Addedv3.2.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the safety envelope: whitelist-only execution, fail-loud rejection on unknown commands, and that arguments are 'less validated' than dedicated tools. The remaining gap is that it never says the dispatched commands can be mutating (undo/PIE/asset writes), so side-effect risk is only implied by the command catalog.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical routing guidance ('prefer the dedicated tool', 'last resort') is front-loaded and each of the first three sentences adds information. The closing bilingual line partially repeats that content and contains garbled mixed-script text ('fail-loud拒绝'), which is wasted space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a generic dispatch tool with no output schema, the description covers scope, discovery path, error behavior, and validation caveats well enough to call it correctly. The one unaddressed item is what a call returns, which varies per underlying command and is left unexplained.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds real value by telling the agent where to obtain a valid `command` value (ue5_tool_search) and by characterizing `params` as less-validated free-form arguments. session_id and idempotency_key semantics are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('run any whitelisted bridge command by name') and quantifies scope as the 'full 101-command surface,' explicitly including capabilities with no dedicated tool (materials, UMG widgets). An agent can immediately tell this apart from the dedicated sibling tools.

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

Usage Guidelines5/5

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

Explicitly states the selection rule: 'Prefer the dedicated tool whenever one exists' and labels itself 'the last resort' — a clear when-not-this-tool clause. It also routes the agent to ue5_tool_search{query} for exact command names rather than guessing.

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