Skip to main content
Glama

unreal_build_scene

Builds an Unreal Engine 5 scene from a structured specification of actors and lights, letting you populate levels programmatically instead of placing each actor by hand.

Instructions

Build a scene from a structured specification of actors/lights.

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

Input Schema

NameRequiredDescriptionDefault
specNo
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 discloses almost nothing: it does not say whether the build replaces or merges with the current scene, whether it is destructive or reversible, what permissions or editor state are required, or how failures are reported. For a scene-constructing mutation tool this is a significant gap, though the phrase 'from a structured specification' at least implies declarative input.

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?

A single front-loaded sentence with no filler, which is structurally clean. However, the brevity here reads as under-specification rather than economy, since critical calling information is absent rather than merely compressed.

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 presence of an output schema relieves the description of explaining return values, and the tool is conceptually simple (one spec in, scene out). Still, with zero annotation coverage and two undocumented parameters, the definition is not complete enough for an agent to call it confidently without inspecting the schema further.

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% for both parameters, and the description only loosely gestures at 'spec' via 'structured specification of actors/lights'. The required 'params' argument has no type, no description, and no explanation of how it relates to 'spec', leaving the agent unable to construct a valid call from the definition alone.

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 names a concrete verb and resource ('Build a scene') and narrows the input to 'a structured specification of actors/lights', which distinguishes it from asset-level operations. It does not, however, differentiate itself from nearby names like unreal_run_build or unreal_optimize_scene, so the agent must infer that this creates scene content rather than compiling or tuning it.

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 tool versus siblings such as unreal_run_build, unreal_get_scene_hierarchy, or unreal_optimize_scene, nor any precondition (editor connected, level open, existing scene replaced vs. appended). Usage must be inferred entirely from the one-line purpose.

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