Skip to main content
Glama

unreal_compile_blueprint

Compile an Unreal Engine Blueprint and return diagnostics, helping you detect errors before running or testing the project.

Instructions

Compile a Blueprint and return diagnostics.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses little. It does not state whether compilation mutates or saves the asset, whether failures raise an error or come back as diagnostics, or whether an editor session is required. "Return diagnostics" is the only behavioral hint, and an output schema already covers returns.

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?

One front-loaded sentence with zero wasted words, which is good structure. However it is sized below what a tool with an entirely undocumented parameter object requires, so the brevity costs more than it saves.

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 values need not be explained. Still, a compile tool with no annotations and a completely undocumented required parameter leaves the agent unable to determine how to invoke it correctly, which is the central gap.

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

Parameters2/5

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

Schema description coverage is 0% and the single required parameter is an opaque, untyped "Params" object. The description says nothing about what that object must contain (asset path, name, flags), leaving the agent with no way to construct a valid call from the definition.

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

Purpose4/5

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

"Compile a Blueprint and return diagnostics" names a specific verb (compile) and resource (Blueprint), so the agent can tell this is not a create/delete/get tool. It does not explicitly differentiate from the sibling unreal_compile_material, though the resource noun makes the distinction inferable.

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

Usage Guidelines3/5

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

Usage is implied by the verb: use this to compile a Blueprint. There is no explicit when-to-use/when-not guidance, no mention of pairing with unreal_get_compile_errors, and no stated prerequisites (e.g., Blueprint must be saved or open).

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