Skip to main content
Glama

Make sound effects

sfx
Idempotent

Produces sound-effect files (up to 16 per call) to embed in an app, game, UI or video. Each item is one of: a role (press, release, toggle_on, toggle_off, continuous_tick, success, warning, notify, complete) with a shared family (seed, character, root, scale) for a coherent UI set with playback hints; a recipe (describe topic=recipes; recipes are starting points) tailored with pitch, bright, dur and seed, pairs alike; or an instrument line with play, which auditions one designed voice. Kinds mix in one call. revise patches a family by its handle. Reports design_mode and loudness; WAV by default, Ogg or Opus on request. Files last 2 h; https://moosetracker.app/acceptable-use.html Schema a964948f.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sfx"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNoOne .zip link (with manifest.json)
itemsNo
styleNoVoice palette; default chip
detailNoAdd per-file diagnostics
familyNoShared identity for a set
formatNoDefault wav; ogg = Vorbis 44.1 kHz; opus = Ogg Opus 48 kHz
reviseNoPatch a family by handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 826121bd"New value: +"Schema a964948f"
  2. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2d544474"New value: +"Schema 826121bd"
  3. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 0781812e"New value: +"Schema 2d544474"
  4. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 0d11f08d"New value: +"Schema 0781812e"
  5. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2d7abb8b"New value: +"Schema 0d11f08d"
  6. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema ff675289"New value: +"Schema 2d7abb8b"
  7. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 2a55f659"New value: +"Schema ff675289"
  8. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 71227a86"New value: +"Schema 2a55f659"
  9. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 64bfe66c"New value: +"Schema 71227a86"
  10. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema eb59845f"New value: +"Schema 64bfe66c"
  11. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 3b8fe45c"New value: +"Schema eb59845f"
  12. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 9b20e675"New value: +"Schema 3b8fe45c"
  13. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema 415a8741"New value: +"Schema 9b20e675"
  14. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Schema d568427c"New value: +"Schema 415a8741"
  15. Changed2 schema fields changed
    • changedInput schema / description
      Previous value: -"Schema 90ddc268"New value: +"Schema d568427c"
    • changedInput schema / properties / items / items / properties / instrument / description
      Previous value: -"Audition one voice: text after iN, e.g. - wave=saw cutoff=45 (describe topic=instrument)"New value: +"Audition one voice: text after iN, e.g. - wave=saw cutoff=45 or sample \"upright-bass\" (describe topic=instrument)"
  16. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"Schema 90ddc268"
  17. Changed3 schema fields changed
    • changedInput schema / properties / items / items / properties / dur / description
      Previous value: -"Target seconds, fitted within 8% or 30 ms"New value: +"Length in seconds, fitted within 8% or 30 ms"
    • changedInput schema / properties / items / items / properties / seed / description
      Previous value: -"0 = plain recipe; other values vary it repeatably"New value: +"0 = plain recipe; others shift pitch, length and tone repeatably (reproducible, not unique)"
    • changedInput schema / properties / items / items / properties / spec / properties / pitch / description
      Previous value: -"Semitones; 12 = octave"New value: +"Semitones; 12 = octave. Lower is heavier, higher lighter"
  18. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, non-destructive, idempotent, closed-world), so the description's job is the extras—and it delivers: 16-file cap, ephemeral 'Files last 2 h', default WAV with Ogg/Opus on request, revise-by-handle patching, and an acceptable-use link. It omits error/failure behavior and any cost or rate context, so not quite exhaustive.

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 assertion and tightly written with no filler sentences. The telegraphic compression ('pairs alike', 'Schema a964948f') costs some readability and the trailing schema hash adds little for an agent.

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

Completeness4/5

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

For a 7-parameter tool with nested objects and no output schema, the description covers what is produced (files, design_mode, loudness), format options, per-call cap, and file lifetime—enough to call it correctly. Gaps remain around zip packaging, variations, detail diagnostics and failure modes.

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 high (86%), so the baseline is 3; the description earns extra credit by encoding cross-parameter relationships the schema never states—family (seed/character/root/scale) belongs with role items, spec (pitch/bright) pairs with recipes, play goes with instrument, revise patches 'a family by its handle'. It leaves zip, variations, detail and style undiscussed in prose, which keeps it off a 5.

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?

Opens with a specific verb+resource ('Produces sound-effect files ... to embed in an app, game, UI or video') and immediately enumerates the three item modes (role+family, recipe+spec, instrument+play), which no sibling (render, song, lyrics, convert) plausibly offers. It also routes capability discovery to the describe tool ('describe topic=recipes'), making the boundary explicit.

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?

Gives real selection guidance between the three in-tool modes: role+shared family for 'a coherent UI set', recipe as 'starting points' tailored by spec, instrument to 'audition one designed voice', and states 'Kinds mix in one call'. It does not explicitly say when to use this versus a sibling like song/render, so it stops short of full alternative routing.

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