Skip to main content
Glama
Sign In

sounds

by com.sfxmint
OverviewDiscussionsAdmin

generate_ambience

Make a continuous environmental sound bed such as rain, waves, a forest or a crowd, not a musical track or an isolated event. Makes 30-second CC0 WAV takes and attempts seamless 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 Ambience; payment_required also returns buy_url. Returns order_id, files and loop_url when available; if pending after about 25 seconds, poll get_generation. Listen in context before use.

Input Schema

NameRequiredDescriptionDefault
promptYesWith enhance=false, describe the audible environment in plain English, at most 400 characters. Name the place and continuous sound bed, its intensity, texture and pace; include occasional events, their spacing and distance only when requested or established by context. Keep it steady and repeatable. Example: 'Gentle ocean waves wash onto a sandy beach and recede at a steady pace, with soft foamy hiss and a low rolling wash.' Preserve the user's sources and spatial details; omit excluded sounds entirely rather than listing 'no music' or 'without voices'. Avoid metaphors that introduce other sources. The server adds the SFX tag and continuous-ambience instruction. With enhance=true, a brief in any language is enough.
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.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the API key/credits/plan prerequisite, that free tries don't apply, the fallback responses (website_url, buy_url on payment_required), the ~25-second pending window and get_generation polling, the 30-second CC0 WAV constraint, and that loops are only attempted and not guaranteed (inspect loop_cut/loop_url). This is exactly the operational context annotations can't carry.

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?

Purpose is front-loaded in the first sentence, followed by prerequisites, return values and polling guidance. It is dense with clauses and a bit telegraphic, but nearly every clause conveys actionable information.

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?

With no output schema, the description shoulders return-value disclosure and does so (order_id, files, loop_url, pending polling). Combined with auth requirements and the loop-not-guaranteed caveat, an agent has everything needed to call and interpret results.

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%, so each parameter is already fully documented in the schema, setting the baseline at 3. The description corroborates the 30-second take length and the returns, but adds no parameter meaning that isn't already in the rich schema descriptions.

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+resource ('Make a continuous environmental sound bed') and immediately excludes the wrong categories ('not a musical track or an isolated event'), which is exactly the distinction needed against siblings like generate_music and generate_sound. An agent can tell what this produces 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 Guidelines4/5

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

The exclusions ('not a musical track or an isolated event') and the 'listen in context before use' guidance give clear context for when this tool applies, and it routes to get_generation for pending jobs. It stops short of naming the sibling tools to use instead for music or one-shot SFX, leaving that inference to the agent.

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