io.github.AudialAI/audial-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Resynthesize a one-shot into a Serum 2 preset

sound2serum

Convert one isolated sound into an editable Xfer Serum 2 preset for reproducing its timbre; use a single note or hit, not loops or melodies.

Instructions

Turn one isolated sound into an editable Xfer Serum 2 preset.

Not for loops or melodies, which give a poor preset. If the result's summary says the match is weak, tell the user and suggest trimming the input to one note.

Input Schema

Name	Required	Description	Default
`file_path`	Yes	One isolated sound: a single note, chord stab or hit, ideally 1-4 s and dry, 20 s at most. Not a loop, melody, drum pattern or anything with several notes in sequence: those produce a poor preset even under 20 s. To use a loop, trim it to one note first. The result is an editable Xfer Serum 2 (.SerumPreset) preset that reproduces its timbre. No plugin needed -- open it in Serum 2.1+.

Output Schema

Name	Required	Description	Default
`tool`	Yes
`files`	Yes
`summary`	Yes
`metadata`	Yes
`output_dir`	Yes
`execution_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.5.0Oct 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already disclose that the tool is non-read-only, open-world, and non-idempotent. The description adds useful behavioral context about poor input types and the weak-match summary workflow, though it does not mention processing time, cost, or where the resulting preset is stored.

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?

The description is short, front-loaded with the core action, and each sentence carries useful guidance. The exclusion and weak-match instruction are directly relevant and not redundant.

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?

With an output schema present, the description need not explain return values. For a one-parameter tool with full schema coverage and annotations, it is nearly complete, though it could explicitly mention the sound2vital alternative for agents choosing between resynthesis targets.

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 description coverage is 100%, and the file_path schema already explains the single-note, dry, length-limited input requirements in detail. The description reinforces the same constraint but does not add parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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 and resource: turning one isolated sound into an editable Xfer Serum 2 preset. It distinguishes the tool from the broader sibling set and from sound2vital by naming Serum 2 explicitly.

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?

It gives clear negative guidance ('Not for loops or melodies') and tells the agent what to do when the match is weak. It does not explicitly route the agent to the sibling sound2vital, but the context for when to use this tool versus general generation tools is clear.

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

Deploy Server