AetherWave Studio

Generate music (Suno)

aetherwave_generate_music

Generates AI music via Suno. Returns two tracks per submission. Default model is V5.5 (newest, best quality). For instrumental output set instrumental: true. Music gen typically takes 30-90s - this tool polls with up to a 6-minute budget. Note: the title param is advisory for instrumentals - Suno often writes its own title from the prompt content for instrumental generations. Transient GENERATE_AUDIO_FAILED errors are common; retry once before degrading the model version.

Returns within ~45 s. If the result has state "running" the job is still rendering: poll aetherwave_get_job with the returned taskId and kind every ~10 s. Pass wait:true ONLY if your MCP client permits tool calls longer than 60 s (most do not). Pass async:true to get the taskId back immediately without waiting.

Input Schema

TableJSON Schema

Name	Required	Description
`wait`	No	Block until the job finishes (up to the tool's full budget, 6-15 minutes). ONLY if your MCP client permits tool calls longer than 60 s; most abandon the call at 60 s and lose the taskId. Default false: return within ~45 s and hand back a taskId if still running.
`async`	No	Submit and return the taskId immediately without polling at all. Then poll aetherwave_get_job(taskId, kind).
`model`	No	Suno model version. Defaults to V5_5 (current best).
`title`	No	Optional title for the generated tracks.
`lyrics`	No	Custom lyrics. If omitted, Suno will generate lyrics from the prompt (unless instrumental=true).
`prompt`	Yes	Style/mood/topic description. E.g. 'Lo-fi ambient track, rain sounds, warm pads' or 'High-energy synthwave with driving bass'.
`audioWeight`	No	0 to 1. Weighting on the audio character of the generation. Only applies with lyrics.
`styleWeight`	No	0 to 1. How closely to follow the style description. Higher sticks to it, lower lets the model roam. Use when someone asks to stay closer to, or further from, a described sound. Only applies with lyrics.
`vocalGender`	No	Vocal gender, 'm' or 'f'. Only applies when lyrics are supplied. Default 'm'.
`instrumental`	No	If true, no vocals. Default false.
`negativeTags`	No	Comma-separated things to AVOID, e.g. 'heavy metal, screaming, distorted guitar'. Use when someone says they do not want a particular sound. Only applies with lyrics.
`weirdnessConstraint`	No	0 to 1. How experimental the result is. Higher is stranger and more unexpected, lower is safer and more conventional. Use when someone asks to make it weirder or more normal. Only applies with lyrics.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

addedInput schema / properties / async

Added value: +{
+  "description": "Submit and return the taskId immediately without polling at all. Then poll aetherwave_get_job(taskId, kind).",
+  "type": "boolean"
+}

addedInput schema / properties / wait

Added value: +{
+  "description": "Block until the job finishes (up to the tool's full budget, 6-15 minutes). ONLY if your MCP client permits tool calls longer than 60 s; most abandon the call at 60 s and lose the taskId. Default false: return within ~45 s and hand back a taskId if still running.",
+  "type": "boolean"
+}

Changed4 schema fields changedAug 12, 2026

addedInput schema / properties / audioWeight

Added value: +{
+  "description": "0 to 1. Weighting on the audio character of the generation. Only applies with lyrics.",
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / negativeTags

Added value: +{
+  "description": "Comma-separated things to AVOID, e.g. 'heavy metal, screaming, distorted guitar'. Use when someone says they do not want a particular sound. Only applies with lyrics.",
+  "type": "string"
+}

addedInput schema / properties / styleWeight

Added value: +{
+  "description": "0 to 1. How closely to follow the style description. Higher sticks to it, lower lets the model roam. Use when someone asks to stay closer to, or further from, a described sound. Only applies with lyrics.",
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / weirdnessConstraint

Added value: +{
+  "description": "0 to 1. How experimental the result is. Higher is stranger and more unexpected, lower is safer and more conventional. Use when someone asks to make it weirder or more normal. Only applies with lyrics.",
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}

Changed1 schema field changedAug 11, 2026

addedInput schema / properties / vocalGender

Added value: +{
+  "description": "Vocal gender, 'm' or 'f'. Only applies when lyrics are supplied. Default 'm'.",
+  "enum": [
+    "m",
+    "f"
+  ],
+  "type": "string"
+}

First observedJun 20, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations declare a non-readonly, non-idempotent, open-world operation, and the description goes further: it discloses the 30-90s typical duration, the 6-minute polling budget, ~45s default return time, returning two tracks per submission, the default model V5.5, the advisory nature of the title param for instrumentals, and the retry directive for transient GENERATE_AUDIO_FAILED errors. This is exactly the behavioral context annotations cannot convey.

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?

Front-loads the core (what it does, track count, default model) then layers operational guidance. Slightly dense with wait/async details that duplicate the schema, but every sentence earns its place for an agent deciding how to call it.

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?

Covers the full lifecycle an agent needs for a long-running, non-idempotent generation call: default polling, wait/async escape hatches, the aetherwave_get_job polling loop, and retry guidance. No output schema, so return-shape info (taskId, kind, state) is carried by the description, which it does. Minor gap: two tracks per submission could be stated alongside the running-state handoff.

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 12 params. The description reinforces a few (instrumental, title, wait, async) but adds no syntax or format info beyond the schema. Baseline 3 is correct when the schema carries semantics.

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 (generates), resource (AI music via Suno), and vendor. Named sibling aetherwave_master_audio handles audio mastering, so the agent can distinguish generation from post-processing. Purpose is unmistakable.

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?

Explicitly covers when to wait vs. async, when to use the instrumental flag, and when to retry on GENERATE_AUDIO_FAILED. It also points the agent to aetherwave_get_job for polling ongoing jobs. Clear conditional routing for the agent.

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

All AetherWave Studio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?