io.github.AudialAI/audial-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Resynthesize a one-shot into a synth preset

sound2vital

Converts a single isolated note, chord stab, or hit into an editable Audial Synth preset, reproducing its timbre. Use dry audio of 1–4 seconds; trim loops to one note first.

Instructions

Turn one isolated sound into an editable Audial Synth 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 Audial Synth (.vital) preset that reproduces its timbre.

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.

Changed1 schema field changedv0.5.0Oct 31, 2026

changedInput schema / properties / file_path / description

Previous value: -"A short one-shot (<= 20 s) audio file. The result is an editable Audial Synth (.vital) preset that reproduces its timbre."New value: +"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 Audial Synth (.vital) preset that reproduces its timbre."

First observedv0.1.1Sep 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations cover the safety profile (writes, open-world, non-idempotent). The description adds real behavioral context beyond that: the result carries a summary that may flag a weak match, and the agent should surface that and suggest trimming input. It doesn't discuss where the preset is written or auth requirements, but with annotations present the added guidance clears the bar.

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?

Two short paragraphs, purpose front-loaded, then exclusions and the weak-match follow-up. The loop restriction appears in both paragraphs, a mild redundancy, but nothing is wasted.

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 one-parameter transform with an output schema, the description covers what an agent needs: input expectations, exclusions, and the one output field worth relaying to the user. Only the destination/permissions of the written preset is left unstated.

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% and the single file_path parameter is already thoroughly documented (duration limits, dry, single note). The description only restates the loop restriction, adding no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource: turn one isolated sound into an editable Audial Synth preset. The target format (Audial Synth, not Serum) implicitly separates it from the sound2serum sibling, though the sibling is never named.

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?

Explicitly says what NOT to use it for (loops, melodies) and why the result is poor, plus a remediation path: trim to one note. It does not point to any alternative tool (e.g., sound2serum, generate_samples) for the excluded cases.

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