Skip to main content
Glama
ChiR24

Unreal Engine MCP Server

by ChiR24

unreal

Search and describe Unreal Engine capabilities, then execute validated actions with precise contracts. Configure internal capability availability to manage what's accessible.

Instructions

Unreal Engine capability gateway. Search first, describe the exact contract, then execute a validated action. Use configure only to manage internal capability availability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolNoExact canonical parent tool name returned by search or describe.
limitNoMaximum search results to return. Defaults to 12.
paramNoExact parameter name (tool-union catalog) to inspect. Requires tool and action for full drill-down; resolves the single parameter schema. Use with describe only.
queryNoSearch words for tools, categories, descriptions, or actions.
actionNoExact action name returned by describe. For configure, this is a manage_tools action.
cursorNoOpaque search cursor from a previous response nextCursor. Supersedes offset.
domainNoCapability domain to browse or filter by. Call describe with no selector to list domains.
effectNoFilter search results by declared behavior effect.
familyNoCapability family inside a domain. Call describe with a domain to list its families.
offsetNoZero-based search result offset. Defaults to 0.
paramsNoParameters for execute or configure. Keys are the action-specific parameter names returned by describe. Never include action or subAction here.
consentNoPer-call consent grant for a capability whose policy.consent is not 'none'. Bound to one capability and one call; never persisted, inherited or reused. Read the exact grant from describe.consentGrant. Use with execute only.
maxBytesNoSerialized byte ceiling for a search response. Results are dropped from the end until the response fits.
operationYessearch finds capabilities. describe returns an exact parent-tool contract. execute runs one validated action. configure manages internal capability availability.
capabilityNoExact canonical capability ID (or declared alias) returned by search, e.g. asset.import. Preferred selector for describe.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
costNo
dataNoExecute payload projected against the capability's declared output schema. Same value as receipt.data, and the same location the native /mcp surface publishes.
toolNo
errorNo
limitNo
paramNo
scopeNoCatalog scope: 'tool' for a tool summary, 'union' for the tool-union parameter catalog.
totalNo
actionNo
domainNo
familyNo
hashesNoPer-record schema and content hashes from the generated catalog.
offsetNo
policyNo
resultNo
schemaNoFull schema of the single described param.
actionsNoPaginated/filterable action list on tool-only describe.
domainsNoBounded domain list on a catalog-level describe.
filtersNoFilters applied to this search.
hasMoreNo
messageNo
outputsNo
reasonsNo
resultsNo
successYes
behaviorNo
familiesNoBounded family list on a domain-level describe.
maxBytesNo
nextCallNoDirectly-invokable gateway request for guided self-correction.
requiredNoWhether the described param is required.
runnableNoFalse when the capability cannot currently be executed; nextCall then points at the fix.
drillDownNoExample nextCall payload to drill one level deeper.
errorCodeNo
operationYes
truncatedNoTrue when results were dropped to fit the byte budget.
capabilityNoCanonical capability ID this response describes.
nextCursorNoCursor to pass back as cursor to continue a search.
parametersNoPaginated/filterable compact parameter catalog on tool+action describe.
parentToolNoLegacy parent tool that dispatches the described capability.
actionCountNo
actionLimitNo
deprecationNo
inputSchemaNoExact input schema of the described capability. Never a parent-tool union.
suggestionsNoClosest-match names for an invalid tool/action/param call.
actionOffsetNo
availabilityNoWhether the capability is available, disabled or unavailable, and why.
capabilitiesNoBounded capability list on a family-level describe.
consentGrantNoExact consent grant this capability requires, ready to pass back as the execute call's consent sibling. Absent when policy.consent is 'none'.
migratedFromNoLegacy tool/action pair that resolved to this capability.
outputSchemaNoExact output schema of the described capability.
actionHasMoreNo
parameterCountNo
parameterLimitNo
catalogRevisionNoRevision of the generated canonical capability catalog this response was served from.
parameterOffsetNo
availableActionsNo
parameterHasMoreNo
perActionSchemasNo
resolvedFromAliasNoDeclared alias that resolved to this capability.
availableParametersNo
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does not mention that execute may have side effects, that destructive capabilities require consent, or any safety or reusability constraints. The description is too terse for a tool that can trigger actions.

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

Conciseness5/5

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

Two sentences, front-loaded with the core purpose, and every word adds value. No redundant information.

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?

Given the tool's complexity (15 parameters, nested objects, output schema), the description provides the essential workflow but omits broader context like the safety implications of execute, consent requirements, or how actions are validated. The schema covers details, but the description alone is not fully complete for a gateway of this scope.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all parameters including operation, search, describe, execute, configure, and consent. The description adds no parameter semantics beyond the schema, but the baseline of 3 applies because the schema does the heavy lifting.

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 'Unreal Engine capability gateway' clearly identifies it as a meta-tool for accessing capabilities, and the workflow 'Search first, describe the exact contract, then execute' clarifies its primary function. It is distinct enough even without sibling tools, though it doesn't use a specific verb+resource pattern.

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

Usage Guidelines5/5

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

The description explicitly instructs the usage order: 'Search first, describe the exact contract, then execute a validated action.' It also provides a specific exclusion: 'Use configure only to manage internal capability availability.' This is clear when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChiR24/Unreal_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server