generate_soundscape

Generate environmental soundscapes from text prompts. Create high-quality background ambience and layered audio textures like rainy forests or distant thunder for any project.

Instructions

Generates immersive, high-quality environmental soundscapes (e.g., 'A rainy forest with distant thunder'). Best for background ambience and complex layered textures. Uses Gemini 2.0 Live.

Input Schema

TableJSON Schema

Name	Required	Description
`prompt`	Yes	The prompt describing the soundscape.
`duration`	No	Optional duration in seconds. Overrides default if provided.
`format`	No	Optional output format (wav, mp3, ogg, flac, etc.).
`bitrate`	No
`sample_rate`	No
`channels`	No
`auto_play`	No	If true, automatically plays the generated audio.

Tool Definition Quality

B3.3/5.0

Behavior3/5

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

Discloses use of Gemini 2.0 Live model but omits other behavioral traits (rate limits, side effects, async nature) since annotations are absent.

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?

Compact three-sentence structure front-loaded with action, no redundancy, every sentence adds distinct value.

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

Completeness3/5

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

Adequate for basic invocation but leaves technical audio parameters unexplained given the moderate complexity of the schema.

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

Parameters2/5

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

With 57% schema coverage and missing descriptions for bitrate/sample_rate/channels, description fails to compensate for these technical audio parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it generates environmental soundscapes with specific examples, and distinguishes from siblings via 'background ambience' and 'complex layered textures' (vs music/SFX/voice).

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

Usage Guidelines3/5

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

Implies usage context via 'Best for background ambience' but lacks explicit when-not-to-use or alternative tool references.

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

Install Server

Gemini Audio MCP