Skip to main content
Glama
Sign In

Soundza

by com.soundza
OverviewDiscussionsAdmin

Generate music

generate_music

Make game music with AI from a text prompt, free. One take per call. Waits for it (loops ~15-30s, full tracks can take longer) and returns a url (WAV) and preview_url (MP3) that need no header, with a ready curl command. Links work for 120 days. Two engines, set by model:

  • "stable" (default): a seamless LOOP for background game music that repeats under a scene. Set looping true. Returns a loop with bpm, bars and seamless:true (and an intro_url when the loop has a lead-in). This is the one that actually loops. Loop the WAV url: the MP3 preview is for listening and has a short gap when repeated.

  • "lyria": a higher-quality FULL-LENGTH track, not a loop. Returns a track. Looping isn't available on lyria. So: looping, repeating background music -> model "stable", looping true. A one-off full piece or higher audio quality -> model "lyria". Describe the music plainly ("warm fantasy village theme, acoustic guitar and flute"). Whenever you know them, pass game (what game it's for), scene (the moment it plays under, e.g. "tense boss fight") and mood (the feel): they make the result fit the game far better, so prefer sending them to leaving them blank. Optional bpm. Takes are AI-generated (ai_content "ai"); tell the person. Separate weekly budgets per model (15 Stable, 8 Lyria). Search the catalog first when an existing track would do.

Input Schema

NameRequiredDescriptionDefault
bpmNoTempo to aim for, in beats per minute.
gameNoWhat game this is for. Improves the result; also tells Soundza what games people want music for.
moodNoThe feel, e.g. "calm and wistful".
modelNo"stable" (default): a seamless loop. "lyria": a full-length, higher-quality track, no looping.
sceneNoThe moment or scene the music plays under, e.g. "tense boss fight".
loopingNoReturn a seamless loop. Stable only (looping with model "lyria" is an error). Default false.
descriptionYesThe music, in plain words. Up to 200 characters.
duration_secondsNoFull tracks only (not loops): length in seconds, 10 to 180.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses blocking/wait times, one take per call, URL formats and no-header access, 120-day link lifetime, AI-generated content disclosure, per-model weekly budgets, and the MP3 preview gap when looping. These are substantive operational details an agent needs before calling.

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?

The description is front-loaded with the core action and return behavior, then organizes the two engines clearly. It is somewhat long and repeats the loop/model routing decision in multiple places, but nearly every sentence provides useful operating context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter generation tool with no output schema, the description covers return values, wait behavior, link lifetime, model differences, looping constraints, budgets, and content disclosure. The remaining gaps are minor because the input schema already documents all parameters at 100% coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about the model/looping interaction, including that looping with 'lyria' is an error and that 'stable' is the default. It also explains why game, scene, and mood matter, though it does not discuss duration_seconds beyond what the schema already says.

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: 'Make game music with AI from a text prompt.' It distinguishes the tool from simple sound generation by explaining the two music engines and by routing catalog searches to another tool when an existing track would suffice.

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?

It gives explicit decision rules: use model 'stable' with looping true for repeating background music, use 'lyria' for a one-off full-length higher-quality track, and search the catalog first when an existing track works. It also tells the agent to prefer supplying game, scene, and mood to improve results.

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

All Soundza toolsInspect
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