Skip to main content
Glama

unreal_get_build_configuration

Retrieves Unreal Engine project build configuration details, enabling AI clients to inspect settings before editing assets or running editor workflows.

Instructions

Get build configuration info.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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 it discloses almost nothing. The verb 'Get' weakly implies a read-only retrieval, but there is no statement about permissions, whether a build must exist first, or what configuration dimensions are returned.

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, but its brevity comes from under-specification rather than efficiency. There is no wasted wording, yet almost no 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?

Although an output schema exists and return values need not be described, the undefined 'params' argument and the absent usage context leave the definition inadequate for invocation. For a tool whose input is opaque, the description should compensate but does not.

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' has no type and 0% schema description coverage, and the description says nothing about it. An agent has no idea what to pass, whether it is an object with expected keys, or whether it can be empty.

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 'Get build configuration info' essentially restates the tool name unreal_get_build_configuration, adding only the vague word 'info'. It does not specify what 'build configuration' covers (target platform, configuration type, project settings) or how it differs from siblings like unreal_build_scene or unreal_run_build.

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 mention of alternatives. An agent cannot tell from the text whether this should be called before a build, to inspect settings, or how it relates to unreal_build_scene/unreal_run_build.

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