Skip to main content
Glama

unreal_run_build

Triggers a build or cook workflow for an Unreal Engine 5 project when the target toolchain supports it, letting you compile and package project content from an AI client.

Instructions

Trigger a build/cook workflow where supported.

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_run_build"
  }
}

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 supplied, the description carries the full disclosure burden for what is inherently a long-running, mutating operation. It does not say whether the call blocks, how long builds typically take, what happens on failure, whether it requires an open editor/plugin context, or what 'cook' changes on disk. Only 'trigger' implies fire-and-forget behavior, which is a minimal signal.

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?

The single sentence is front-loaded and free of padding, so there is no verbosity problem. The issue is the opposite of wordiness: the sentence is too thin for the tool's complexity, and the trailing 'where supported' is a vague qualifier that consumes space without informing.

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-value explanation is not required. But for a build-trigger tool with an opaque required parameter, no annotations, and a vague capability caveat, the definition omits the essentials: how to supply params and what execution model to expect. It is not sufficient to call this tool correctly.

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 is an untyped, undescribed 'params' object at 0% schema description coverage, and the description says nothing about what belongs in it. An agent has literally no basis for constructing a valid argument beyond guessing, so the description fails to compensate for the schema gap.

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 specific action and resource ('Trigger a build/cook workflow'), which is more than a restatement of the name. However, 'where supported' hedges the scope without saying what makes it unsupported, and nothing distinguishes this from siblings like unreal_build_scene or unreal_get_build_configuration. The agent can guess the purpose but cannot confidently discriminate.

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 prerequisites, and no named alternative. The only conditional hint is 'where supported', which states a constraint exists without telling the agent how to determine it, so selection between this and the other build-related siblings is left entirely to inference.

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