UE Audio MCP

Overview Schema Source Related Servers Discussions Admin

build_aaa_project

Build a complete AAA audio project by generating Wwise infrastructure and Wwise, MetaSounds, and Blueprint content per category, then routing outputs and organizing work units.

Instructions

Build a complete AAA audio project: infrastructure + content for all categories.

Creates AAA Wwise infrastructure (buses, work units, switches, states), then generates 3-layer content (Wwise + MetaSounds + Blueprints) for each audio category, routes outputs to correct buses, and moves objects to dedicated work units.

Auto-detects connection state:

Full (Wwise + UE5): creates infrastructure, builds all content, routes + moves
Wwise-only: creates infrastructure, builds Wwise content, returns MS commands
Offline: returns complete manifest of what would be created (dry-run)

Args: categories: Comma-separated category filter (default: all). Available: player_footsteps, player_weapons, npc_footsteps, ambient_wind, weather, ui setup_params: JSON overrides for template_aaa_setup, e.g. {"include_reverbs": false}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`categories`	No
`setup_params`	No		{}

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.2Oct 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it describes auto-detection of connection state, side effects (infrastructure creation, content generation, routing, moving objects), and the offline dry-run return. It still omits idempotency/overwrite behavior and permission requirements, so it is strong but not fully exhaustive.

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

Conciseness4/5

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

The description is front-loaded with the core purpose, then structured into mode behaviors and an Args section. It is appropriately sized for a complex build tool, though it is long enough that a few additional trims would be possible without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, the lack of annotations, and the presence of an output schema, the description is complete enough to call it correctly. It covers purpose, connection-state behavior, parameter semantics, and expected outcomes (commands/manifest) without needing to duplicate return-value documentation.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It documents both parameters well: categories as a comma-separated filter with default all and an explicit list of valid values, and setup_params as JSON overrides with a concrete example key and value.

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

Purpose5/5

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

The description states a specific verb (Build) and a compound resource (AAA audio project: infrastructure + content for all categories). It also enumerates the concrete outputs (Wwise buses/work units/switches/states, 3-layer content, bus routing, work unit moves), which lets an agent distinguish this from narrower siblings like template_aaa_setup or build_audio_system.

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

Usage Guidelines4/5

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

The description provides clear usage context by explaining the auto-detected connection states and the resulting behavior in each mode (full, Wwise-only, offline dry-run). However, it does not explicitly name alternatives or give when-not-to-use guidance against sibling tools such as build_audio_system or template_aaa_setup.

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

Deploy Server