Import or bind sounds, play audio, spawn Niagara effects, set their parameters, and create sequences in a running Unreal editor.
Audio, Niagara and Sequencer: import_sound / bind_sound / play_sound / spawn_niagara / set_niagara_parameter / create_sequence.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | ||
| params | No | ||
| timeout | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It reveals only that actions like import_sound and spawn_niagara exist, implying mutation, but says nothing about side effects on assets or levels, permissions, reversibility, or the dispatch semantics of the action/params/timeout trio.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a single compact line with the domain grouping front-loaded, so there is no padding. However, the compression goes too far: the slash-separated token list reads as under-specification rather than tight, purposeful prose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations, no output schema, 0% parameter documentation, and a free-form nested `params` object, this description is far short of what an agent needs to invoke the tool reliably. Missing are the action-to-parameter mapping, return behavior, and any failure/timeout semantics.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for three parameters, including a nested, untyped `params` object. The description implicitly enumerates valid `action` values but does not state which params each action accepts, what `timeout` governs, or how `params` is shaped — a significant compensation gap for the most important schema field.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names three domains (Audio, Niagara, Sequencer) and enumerates six concrete action strings, which lets an agent infer this is a media/asset operation dispatcher for Unreal Engine. However, it never states the tool's purpose in a verb+resource form, and the domain labels are only implicit differentiation from siblings like ue_material or ue_blueprint.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use / when-not-to-use guidance and no mention of the sibling tools (ue_world, ue_blueprint, ue_material, etc.) that an agent must choose between. The listed actions imply scope, but nothing routes the agent away from the wrong tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.