Skip to main content
Glama
Sign In

sounds

by com.sfxmint
OverviewDiscussionsAdmin

generate_music

Make instrumental background music (BGM), including ambient music, for an app or game; for environmental sounds use generate_ambience. Makes 30-second CC0 WAV takes and attempts to extract repeating musical loops. Needs an SFXMint API key and credits or a plan; sound-effect free tries do not apply. Missing access returns website_url for Studio BGM; payment_required also returns buy_url. Returns order_id, files and loop_url when available; if pending after about 25 seconds, poll get_generation. Supports instrumental music, not intelligible vocals or lyrics; clarify a vocal request with the user instead of silently substituting. Listen in context before use.

Input Schema

NameRequiredDescriptionDefault
promptYesWith enhance=false, write a plain English instrumental music description, at most 400 characters, usually 1-3 sentences. State the genre, instruments and what they play, mood, energy and tempo (BPM if specified). Preserve named genres, instruments and pace; choose compatible instrumentation only when the brief leaves it open. Describe a repeating motif and steady accompaniment suitable for a background loop. Example: 'A calm fantasy instrumental loop at 80 BPM, with gentle harp arpeggios, warm sustained strings and a simple flute melody, keeping a steady, hopeful mood.' Use positive audible terms; omit unwanted sources instead of naming them in exclusions. Avoid artist, song or game names, lyrics and the 'TrackType: SFX' tag. With enhance=true, give the musical brief in any language and the music writer adapts it.
enhanceNoDefault false. Write final English using this tool's prompt guidance to skip server AI rewriting. True asks the corresponding ambience or music writer to adapt a brief in any language; enhanced_prompt reports the result. Non-Latin input may still require server translation with false.
duration_sNoTake length, fixed at 30 seconds; omit or pass 30. A returned loop may be shorter. A loop is not guaranteed: inspect loop_cut and loop_url.
variationsNoHow many takes to make (default 4; one generation either way)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the generic write/no-destroy profile; the description adds substantial beyond-schema behavior: 30-second CC0 WAV takes, best-effort loop extraction, missing-access returns website_url via studio_list_link patterns, payment_required returns buy_url, and the ~25s pending threshold. That is exactly the operational context an agent needs to avoid a failed call loop.

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-loaded with purpose and the sibling boundary, and every clause carries actionable information (access, return shape, polling, vocal limitation). It is dense with semicolon-joined clauses, making it slightly harder to scan than a bulleted equivalent.

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?

No output schema exists, yet the description names the returned fields (order_id, files, loop_url, enhanced_prompt, loop_cut) and the async polling path. Combined with auth/credit prerequisites and the instrumental-only constraint, an agent has everything needed to call it and handle outcomes.

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 each parameter already carries rich, self-contained guidance (prompt crafting, enhance semantics, fixed 30s duration, variations enum). The description adds little parameter-level detail beyond the fixed 30-second take and loop caveat, so baseline 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?

States a specific verb and resource (make instrumental background music, including ambient music, for apps/games) and immediately names the sibling boundary: environmental sounds belong to generate_ambience. It also rules out a whole category (intelligible vocals/lyrics), so an agent can distinguish it from generate_sound and generate_ambience without opening a 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?

Explicit routing: use generate_ambience for environmental sounds, poll get_generation if pending after ~25 seconds, and clarify a vocal request with the user rather than silently substituting. It also states the access precondition (API key + credits or plan; sound-effect free tries do not apply).

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

All sounds 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