UE Audio MCP

Overview Schema Source Related Servers Discussions Admin

ms_preset_morph

Build a MetaSound Source that interpolates parameters between two presets via a 0.0-1.0 Morph input, enabling dynamic audio blending in Unreal Engine.

Instructions

Build a MetaSound Source that morphs between two parameter sets.

Creates a Source with a Morph input (0.0-1.0) that smoothly interpolates each parameter between set A (Morph=0) and set B (Morph=1). Uses Map Range nodes for each parameter and InterpTo for smooth transitions.

Args: name: Name for the morph MetaSound asset param_set_a_json: JSON object of param_name -> value at Morph=0 param_set_b_json: JSON object of param_name -> value at Morph=1 asset_path: Content path for the output asset

Input Schema

TableJSON Schema

Name	Required	Default
`name`	Yes
`asset_path`	No	/Game/Audio/Generated/
`param_set_a_json`	Yes
`param_set_b_json`	Yes

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

A3.8/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 burden and does well: it discloses that the tool constructs Map Range nodes per parameter and InterpTo transitions, and that the morph input operates on a 0.0-1.0 range. It omits overwrite/asset-collision semantics and creation failure behavior, which matter for a mutating asset-creation tool, keeping it short of a 5.

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 purpose sentence is front-loaded, followed by the interpolation mechanics and then an Args block. The Args block partly duplicates the schema, but given 0% schema description coverage that duplication is functional rather than wasteful.

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

Completeness4/5

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

For a graph-construction tool with an output schema and no annotations, the description covers purpose, morph semantics, and every parameter. It stops short of covering overwrite behavior or what happens on invalid, but an agent has enough to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and the Args block documents all four parameters including the defaulted asset_path, which the raw schema leaves as bare titles. It adds meaning (set A at Morph=0, set B at Morph=1) but does not specify the JSON value typing or the required shape beyond 'param_name -> value'.

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 gives a specific verb and resource: it builds a MetaSound Source that morphs between two parameter sets, with the morph semantics (Morph 0.0-1.0 interpolating set A to B) spelled out. It does not, however, name or contrast with any sibling such as ms_preset_swap or ms_create_source, which is the natural alternative an agent would weigh.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is for creating a parameter-morphing source, but there is no explicit when-to-use, when-not-to-use, or routing to alternatives like ms_preset_swap or ms_create_source. The morph range is stated but is a mechanic, not guidance about choosing this tool.

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

Deploy Server