Skip to main content
Glama

unreal_compile_material

Compiles a material in an Unreal Engine 5 project via UnrealEngineMCP, applying material graph changes so the asset is ready for rendering and editor use.

Instructions

Compile a material.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/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 and delivers none of it: whether compilation mutates/saves the asset, whether it requires the editor to be open, whether errors are surfaced, or how expensive the operation is remain unknown. The presence of an output schema covers the return shape, which is the only reason this isn't a 1.

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

Conciseness2/5

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

At four words the text is certainly brief and front-loaded, but its shortness is under-specification rather than efficiency — no sentence earns its place because no useful information is conveyed.

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?

For a compile operation with no annotations, an opaque nested parameter, and no documented side effects, this definition is far from complete. Only the existence of an output schema keeps the score above the minimum.

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 'params' is an untyped object with 0% schema description coverage and no properties, and the description says nothing about what must be supplied (material path, name, options). With one opaque parameter and zero compensation in the description, an agent cannot construct a valid call.

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

Purpose2/5

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

The description restates the tool name verbatim ('Compile a material' for unreal_compile_material) with no added scope, target asset identification, or distinction from siblings like unreal_compile_blueprint or unreal_get_compile_errors. An agent learns nothing it couldn't infer from the name alone.

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 use this versus unreal_get_compile_errors (check results), unreal_save_material (persist), or unreal_compile_blueprint. No prerequisites, no sequencing, no exclusions are stated.

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