Skip to main content
Glama

ue_build_unblock

Identify and terminate processes that hold the Unreal Engine build lock, clearing blocked builds and infinite waits.

Instructions

Trova — e se vuoi termina — i processi che tengono occupato il lock di build.

Serve quando ue_build_status riporta blocked: gli script di Epic prendono un lock globale e un'istanza rimasta orfana non lo rilascia mai, quindi Build.bat aspetta all'infinito e ogni nuovo tentativo si accoda.

La ricerca è sulla riga di comando, non sul nome dell'immagine: su UE 5 UnrealBuildTool è un assembly .NET dentro dotnet.exe e gli script girano dentro cmd.exe, quindi nessuno dei due si trova con taskkill /IM UnrealBuildTool.exe — ed è il motivo per cui il lock sembra inestirpabile.

Args: dry_run: con True (default) elenca soltanto. La ricerca per riga di comando può intercettare un dotnet.exe che sta facendo altro: guarda l'elenco prima di terminarlo. engine_version, engine_root: quale motore, per sapere quale file di lock controllare (%TMP%\<percorso di Build.bat>.lock).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNo
engine_rootNo
engine_versionNo
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses key behaviors: search by command line, termination optional via dry_run, and lock file location. While it could explicitly state 'destructive' for the non-dry-run mode, the term 'terminates' implies this. The explanation of why command-line search is necessary adds useful transparency.

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 description is front-loaded with purpose, then usage scenario, then technical reason, then parameter details. It is efficient but slightly long; however, every sentence adds value. No wasted words.

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 tool with 3 parameters and no output schema, the description covers the trigger condition, the locking mechanism, parameter semantics, and the dry_run safeguard. It does not specify return format, but the context is sufficient for an agent to decide when and how to invoke it.

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 0%, but the description compensates well. It explains dry_run (default true, only lists), and that engine_version/engine_root determine which lock file to check. This adds context beyond the schema's title and type, helping the agent use parameters correctly.

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 the verb 'finds and terminates' and the resource 'processes holding the build lock'. It distinguishes from siblings like ue_build_status by specifying the exact scenario (when status reports 'blocked'), making the tool's purpose unique and actionable.

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?

It explicitly tells when to use this tool: when ue_build_status reports 'blocked'. It explains why typical approaches fail (scans command line, not image name) and advises using dry_run first to avoid killing unrelated processes. This provides clear usage guidelines.

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