Skip to main content
Glama

ue_editor_open

Opens a Unreal Engine project in the editor and waits for the MCP bridge to become ready. If the bridge isn't ready, poll the editor status until it reports bridge_ready.

Instructions

Apre un progetto nell'editor e attende che il bridge risponda.

L'attesa predefinita è breve di proposito: molti client MCP interrompono una richiesta dopo 60 secondi, e un wait_seconds più lungo faceva fallire la chiamata con "Request timed out" anche quando l'editor era partito benissimo. Se il bridge non è ancora pronto la risposta lo dice e basta richiamare ue_editor_status finché running diventa bridge_ready.

Args: uproject: percorso del file .uproject. engine_version: forza una versione del motore diversa da quella associata. wait_seconds: quanto attendere il bridge. Il primo avvio compila gli shader e può volerci molto di più: in quel caso non alzarlo oltre il timeout del client, si fa polling con ue_editor_status. extra_args: argomenti aggiuntivi per la riga di comando dell'editor. engine_root: percorso del motore, quando non è registrato nel sistema. skip_module_check: lancia anche se i moduli C++ non corrispondono al motore (l'editor resterà bloccato su una modale dietro allo splash).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uprojectYes
extra_argsNo
engine_rootNo
wait_secondsNo
engine_versionNo
skip_module_checkNo
Behavior5/5

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

Explains the default wait is short due to client timeout, the risk of timeout despite editor starting, and the behavior of skip_module_check causing a modal. Adds significant context beyond bare annotations (none provided).

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?

Well-structured with main action first, then an important note about waiting, then parameter documentation. Slightly verbose but every sentence adds value.

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?

Covers waiting behavior, parameters, and suggests polling. Missing explicit mention of return value format, but the context of opening and waiting is complete enough given tool complexity.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining each of the 6 parameters, including practical advice for wait_seconds and consequences of skip_module_check.

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?

The description clearly states it opens a project in the editor and waits for the bridge. This distinguishes it from siblings like ue_editor_status and ue_editor_close.

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

Usage Guidelines4/5

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

Provides guidance on waiting behavior, suggests polling with ue_editor_status if bridge isn't ready, and warns against setting wait_seconds too high. Lacks explicit comparison to other opening alternatives but still useful.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FFZackFair92/unreal-engine-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server