Skip to main content
Glama

Doseedo Film Score: spot a video, play your score on AI instruments, mix it to picture

Generate sound effects (SFX & foley)

doseedo_generate_sound

SOUND EFFECTS (SFX) from words with Stable Audio Open — SOUND DESIGN and FOLEY for game audio, apps and video: impacts, whooshes, door slams, footsteps, UI blips, creature and sci-fi sounds, ambiences ("rain on a tin roof", "busy café"), risers, drum one-shots. A one-shot hit ("punchy house kick", "snare with a short room", "a riser into the drop"), a loop on the tempo grid ("glitchy percussion"), or a texture ("vinyl crackle", "rain"). kind picks which (hit | loop | texture); omitted, the server reads it off the words. Don't put a tempo in a hit's prompt — tempo words make it write a loop. Wrong tool for a part with notes (doseedo_render_midi) or a piece of music (you write it; doseedo_render_score plays it). Async: job_id → doseedo_wait_task (typically 15–40 s) → audio URLs (pre-signed: curl -OJ , no auth header, valid 24 h). Each sound is one 30 s window = 10 credits: before sending a batch, doseedo_quote {job: "generate_sound"} or doseedo_account says how many the account has room for now. Cancel: a render that has not reached the GPU yet is stopped and its credits refunded; one already rendering finishes on the GPU (its credits are spent), the job ends as canceled and the output is discarded.

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": "doseedo_generate_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
bpmNoTempo a loop is cut to (default 120).
kindNohit = one sound (0.5–10 s), loop = 1–4 bars tiled at bpm, texture = a bed. Default: read off the prompt.
nameNoOptional: a name for this job's files, e.g. "rainy-loop-3". Every file it returns downloads as <name>_<part>.<ext> (rainy-loop-3_Celesta.wav, rainy-loop-3_rough-mix.wav; one take: rainy-loop-3.wav), so the user can find them. Give each job its own name (a second take: "rainy-loop-3b"). Default: doseedo-<last 6 characters of the job id>.
seedNoOptional random seed for reproducibility.
promptYesWhat it sounds like, e.g. "punchy house kick drum, single hit" or "dusty vinyl crackle". ≤ 300 characters (a longer one is cut at a word boundary, with a warning).
time_signatureNoMeter a loop is cut to, e.g. "4/4" (default).
idempotency_keyNoOptional. Any unique string for THIS request (e.g. a UUID). Re-sending the same call with the same key after a timeout returns the same job instead of starting a second one.
duration_secondsNoLength in seconds. Default: 2 s for a hit, 4 bars at bpm for a loop, 8 s for a texture.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / prompt / description
      Previous value: -"What it sounds like, e.g. \"punchy house kick drum, single hit\" or \"dusty vinyl crackle\". ≤ 300 characters."New value: +"What it sounds like, e.g. \"punchy house kick drum, single hit\" or \"dusty vinyl crackle\". ≤ 300 characters (a longer one is cut at a word boundary, with a warning)."
    • addedInput schema / properties / prompt / maxLength
      Added value: +300
  2. Changed1 schema field changed
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Optional: a name for this job's files, e.g. \"rainy-loop-3\". Every file it returns downloads as <name>_<part>.<ext> (rainy-loop-3_Celesta.wav, rainy-loop-3_rough-mix.wav; one take: rainy-loop-3.wav), so the user can find them. Give each job its own name (a second take: \"rainy-loop-3b\"). Default: doseedo-<last 6 characters of the job id>.",
      +  "maxLength": 80,
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations only declare the generic profile (not read-only, open-world, non-destructive, not idempotent), so most behavioral burden falls on the description, which delivers strongly: async job_id flow, ~15-40 s wait via doseedo_wait_task, pre-signed URLs needing no auth header and valid 24 h, cost of 10 credits per 30 s window, and precise cancel semantics distinguishing pre-GPU (refunded) from mid-render (credits spent, output discarded). The only real gap is that idempotentHint=false sits alongside an idempotency_key parameter without the description reconciling what re-sending does outside a timeout.

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 resource and its use cases, then capability, then async/cost/cancel mechanics in a logical order. The long SFX noun list is verbose but functional for prompt matching; a couple of parenthetical examples could be trimmed without losing meaning.

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 carries the return-value burden and does so: audio URLs, pre-signed download usage (curl -OJ, no auth header, 24 h), and file naming conventions. Combined with the async lifecycle, cost, and cancellation behavior, an agent has everything needed to invoke and follow up correctly.

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; the description earns above that by explaining how kind interacts with the prompt ('kind picks which... omitted, the server reads it off the words') and by warning that tempo words in a hit prompt flip the result to a loop — non-obvious semantics an agent could not infer from the enum alone. It does not discuss seed, name, or duration_seconds, which the schema already covers well.

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 ('SOUND EFFECTS (SFX) from words with Stable Audio Open') and enumerates the sound families it covers — impacts, whooshes, footsteps, UI blips, ambiences, risers, drum one-shots. It also explicitly names the siblings it is NOT for (doseedo_render_midi for parts with notes, doseedo_render_score for music), so an agent can route without opening another 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?

Gives explicit when-to-use (SFX/foley categories with example prompts) and when-not (melodic parts, full music), plus an operational prerequisite: run doseedo_quote or doseedo_account before a batch to check credit room. It even supplies a negative prompting rule — don't put tempo in a hit's prompt because tempo words produce a loop.

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.

Resources