Skip to main content
Glama

unreal_get_compile_errors

Retrieve recent Unreal Engine compile errors to diagnose build failures and guide targeted fixes in your project.

Instructions

Get recent compile errors.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses almost nothing beyond the read implication of 'Get'. 'Recent' is undefined (time window? session? last compile only?), and it does not say whether this triggers a compile, caches results, or requires the editor to be connected.

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 waste, but the brevity crosses into under-specification rather than economy. 'Recent' is the only qualifier and it is left ambiguous.

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 structure need not be described, but with no annotations and a completely undocumented required parameter, the definition leaves too much for the agent to guess. A sentence on the 'params' payload and the scope of 'recent' would make it callable with confidence.

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?

Schema coverage is 0% and the single required 'params' property has no type or documented fields, making the schema effectively opaque. The description does not compensate at all — it gives no hint about what belongs in 'params' (filter severity? limit? asset path?).

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?

The description pairs a clear verb ('Get') with a specific resource ('recent compile errors'), so an agent knows the kind of data returned. It does not differentiate from the sibling 'unreal_get_errors', leaving ambiguous whether general editor errors are included or how 'recent' is bounded.

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 guidance on when to call this versus 'unreal_get_errors' or the compile_blueprint/compile_material siblings, nor any prerequisites (e.g., whether a compile must already have run). The reader must infer usage entirely from the name.

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