Skip to main content
Glama
NAJEMWEHBE

unreal-ai-connection

compile_mod_pak_direct

Compile UE5 mods into .pak files by invoking UnrealPak.exe directly, bypassing RunUAT when it is broken. Requires pre-cooked assets.

Instructions

Compile a UE5 mod into a .pak by invoking UnrealPak.exe directly with a response file, bypassing RunUAT entirely. Use when the Dev Kit's RunUAT BuildMod is broken (Funcom Conan Exiles Enhanced UE5 ships a ScriptModules manifest invalid-record bug — UAT deletes its own deps.json before BuildMod can run). Pre-condition: caller has already cooked the .uasset files (e.g. via execute_unreal_python on a running Editor, or a separate UnrealEditor-Cmd.exe -run=Cook pass). UnrealPak is a standalone UE binary and works regardless of UAT state — runs in seconds and produces a .pak that deploys directly to the server's Mods// folder. Complements compile_mod_pak (which uses RunUAT); use compile_mod_pak_direct when UAT is broken on your Dev Kit. SYNTHETIC bridge-side handler.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unreal_pak_pathYesAbsolute path to UnrealPak.exe (e.g. <DevKit>/Engine/Binaries/Win64/UnrealPak.exe)
response_fileYesAbsolute path to UnrealPak response file (.txt). Each line maps an absolute source path to a mount point inside the .pak, in the standard UnrealPak format: "<absolute_source>" "<mount_in_pak>"
output_pakYesAbsolute path where the .pak should be written (created if parent dir missing; required so success can be verified)
compressionNoCompression algorithm (passed as -compress<Algo> flag); 'None' omits the flag entirely (uncompressed pak)Zlib
extra_argsNoAdditional CLI args appended to UnrealPak.exe (e.g. -encryptionkey)
timeout_secNoMax wait time in seconds; default 600 (10 min) — UnrealPak is typically much faster than RunUAT
Behavior4/5

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

With no annotations, the description fully bears the burden. It explains the tool bypasses RunUAT, runs in seconds, produces a .pak for direct deployment, and requires pre-cooked files. It also labels itself as 'SYNTHETIC bridge-side handler'. While it lacks details on failure modes, it still provides substantial behavioral context.

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

Conciseness5/5

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

The description is concise (about 6 sentences), front-loaded with the core purpose and differentiator. Every sentence adds valuable information without redundancy.

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

Completeness3/5

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

The description lacks explicit information about the tool's return value or output format. It says 'produces a .pak' but doesn't specify what the tool returns (e.g., success message, path). Given the tool has no output schema, this omission leaves a gap.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal extra meaning beyond the schema, meeting the baseline but not exceeding it.

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 tool's purpose: 'Compile a UE5 mod into a .pak by invoking UnrealPak.exe directly'. It also distinguishes it from sibling tool compile_mod_pak, specifying when to use each. This provides excellent clarity.

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?

The description explicitly advises when to use this tool: 'Use when the Dev Kit's RunUAT BuildMod is broken' due to a specific bug. It also contrasts with compile_mod_pak. This offers precise usage guidance.

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/NAJEMWEHBE/unreal-ai-connection'

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