Skip to main content
Glama

Sound Generation

sound-generate
Read-only

Generate sound effects and short music tracks from text prompts (NOT speech: use tts for spoken voice). Returns the audio as base64 with its format, sample rate and duration. Use for sound effects, ambience and short instrumental music. It produces no spoken words: for speech use tts. Cost: 4 credits, charged only when a call succeeds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "sound-generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesDescription of the sound effect or music to generate. NOT for speech (use tts for spoken voice).
output_formatNoAudio format and quality.mp3_44100_128
duration_secondsNoLength of generated audio in seconds (0.5 to 22). Leave unset to let the model auto-decide based on the prompt.
prompt_influenceNoHow strictly to follow the prompt (0.0 = creative, 1.0 = literal). Default 0.3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe, non-destructive, closed-world read, so the description only needs to add context beyond that — and it does: it discloses the return payload (base64 audio plus format, sample rate, duration) and the billing behavior (4 credits, charged only on success, i.e. no charge on failure). Those are exactly the operational traits an agent cannot infer from the annotations.

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 the core purpose and the speech exclusion, and every sentence carries operational weight. It loses a point for restating the 'not speech, use tts' exclusion three times across the description, which is redundant.

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 a four-parameter generation tool with no output schema, the description covers purpose, exclusions, alternative routing, return payload, and cost. An agent has everything needed to decide and invoke correctly.

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 every parameter — prompt, output_format enum, duration_seconds range with auto-decide behavior, prompt_influence scale — is already documented in the schema. The description adds no syntax, format, or interaction detail beyond that, so the baseline of 3 applies.

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 ('Generate sound effects and short music tracks from text prompts') plus the negative scope ('NOT speech'), and names the sibling (tts) that covers the excluded case. An agent can distinguish it from tts and stt without opening any 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?

Explicitly says when to use ('sound effects, ambience and short instrumental music') and when not to ('for speech use tts'), naming the alternative. It also gives a cost threshold (4 credits, charged only on success) that helps an agent decide whether a call is worth making.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.