io.github.AudialAI/audial-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Generate music

generate_music

Create new or transformed music from text prompts and audio files, including songs, covers, remixes, and track-focused re-renders. Use it for generation, not for editing an existing mix.

Instructions

Generate music with the Audial music model.

Text to music, covers, remixes, lego (re-render with one track emphasised), or analysis (understand). Use for new or transformed music, not to edit an existing mix: that is master or stem_split. Takes a few minutes and counts as one run, and audio goes to a new results folder.

Input Schema

Name	Required	Description	Default
`bpm`	No	Tempo hint in beats per minute.
`seed`	No	Seed for reproducible output.
`lyrics`	No	Lyrics with optional section tags like [Verse] and [Chorus]. Omit for instrumental.
`prompt`	Yes	Style description: genre, mood, instruments, vocal character. Tempo and key words in the prompt steer the model more than the numeric bpm/key fields, which are hints, not constraints.
`key_scale`	No	Key hint, e.g. 'G major'.
`task_type`	No	text2music (default), cover, remix, lego, or understand.	text2music
`batch_size`	No	Number of variations, 1-8.
`track_name`	No	Track to emphasise for lego: vocals, drums, bass, guitar, piano, strings, synth, other.
`source_file`	No	Local audio file; required for remix, lego, understand.
`audio_format`	No	mp3, wav, flac, opus or aac.	mp3
`instrumental`	No	Generate without vocals.
`audio_duration`	No	Length in seconds (10-600).
`reference_file`	No	Local audio file; required for cover.
`repainting_end`	No	Remix end time in seconds (-1 = end).
`time_signature`	No	e.g. '4/4'.
`vocal_language`	No	Language code for vocals, e.g. 'en'.	en
`negative_prompt`	No	What to avoid, comma-separated.
`repainting_start`	No	Remix start time in seconds.
`audio_cover_strength`	No	0-1 fidelity to the original for cover/remix.

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.

Changed3 schema fields changedv0.5.0Oct 31, 2026

changedInput schema / properties / source_file / description

Previous value: -"Local audio file; required for remix, extract, lego, complete, understand."New value: +"Local audio file; required for remix, lego, understand."

changedInput schema / properties / task_type / description

Previous value: -"text2music (default), cover, remix, extract, lego, complete, or understand."New value: +"text2music (default), cover, remix, lego, or understand."

changedInput schema / properties / track_name / description

Previous value: -"Track to extract/replace for extract/lego: vocals, drums, bass, guitar, piano, strings, synth, other."New value: +"Track to emphasise for lego: vocals, drums, bass, guitar, piano, strings, synth, other."

First observedv0.1.1Sep 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the write/non-deterministic profile is known. The description adds genuinely non-structured context: the call takes a few minutes, consumes one run (a cost signal), and output lands in a new results folder. It does not mention auth/permission requirements, which keeps it below 5.

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?

Four short sentences, purpose first, then alternatives, then cost and output behavior. Every clause carries information an agent would otherwise have to guess; no filler.

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 19-parameter generative tool with an output schema and full annotation coverage, the description covers purpose, routing, latency/cost, and output location. The only gap is that per-mode prerequisites (source files for remix/lego/understand) live solely in the schema, but that is acceptable given 100% schema coverage.

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%, so the schema already documents all 19 parameters including which task types require source_file or reference_file. The description only adds a plain-language gloss on the task_type values ('lego (re-render with one track emphasised)', 'analysis (understand)'), which is marginal added meaning over the structured fields.

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?

States a specific verb and resource (generate music with the Audial model) and then enumerates the actual modes: text2music, cover, remix, lego, understand. It explicitly distinguishes itself from master and stem_split, so an agent can route without opening the schema.

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

Usage Guidelines5/5

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

Gives both the positive case ('new or transformed music') and the exclusion ('not to edit an existing mix'), and names the sibling tools that handle the excluded case. That is a complete routing rule.

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