Skip to main content
Glama
Sign In

sounds

by com.sfxmint
OverviewDiscussionsAdmin

search_sounds

Read-only

Free-text search over the SFXMint library of free CC0 sound effects. Use it for sound descriptions, additional constraints or gaps left by another tool. Choose get_role_sound for a named event or get_sound_set for multiple events when that fits the task; these are task branches, not a fixed sequence. Hard constraints (duration, loop, format, excluded words) always apply. results hold sounds whose text has every word of the query. When there are none, closest lists the nearest sounds that meet every hard constraint, best first, each with missing_terms: judge them from title and description and let the user listen. library_fit says how well the library covers the request (full, close, weak, none); anything short of full also returns generation options (generate_available; type ambience or bgm for looping environments or background music; use its mcp_tool when present and authorized, or its Studio page). Returns direct, hotlinkable MP3/WAV URLs and verified OGG (Vorbis) URLs where available — no API key, no attribution required — plus acoustics measured from the WAV (onset_ms, peak_ms, audible_ms, attack_ms, tail_ms, centroid_hz, peak_dbfs, rms_dbfs), character labels like 'bright · punchy · tight', loop/file-QC status, and score/match as ranking evidence only (role = known role default, exact = all words hit, partial = some words hit, semantic = nearest by meaning).

Input Schema

NameRequiredDescriptionDefault
loopNoRequire (true) or exclude (false) a candidate marked with prepared loop metadata; seam evidence is returned separately.
limitNoMax results (default 10, max 50)
queryYesUse concise English search terms for the source or event, action and essential audible traits from the user's request or project context: 'door slam', 'soft UI confirmation chime', 'coin pickup'. A single clear source such as 'thunder' is valid; do not pad it. Translate other languages while preserving meaning. Avoid full generation prompts, app backstory, synonym lists and invented materials or environments: full matches must cover every query word. Put duration, loop and format requirements in their separate fields. If no full match exists, inspect closest and missing_terms; simplify only optional wording, never silently drop a required trait.
formatNoDelivery format (ogg = Ogg Vorbis, only sounds published before 2026-10-14 have it); loop=true defaults to WAV when omitted.
categoryNoOptional category slug: ui, retro-game, transition, impact, ambience, water, fire-electric, footsteps, door, mechanical, paper-fabric, glass, animal, crowd, cartoon, magic-scifi, horror, feedback, instrument, office, human, vehicle, household
max_duration_msNoHard maximum length of the sound in milliseconds: a file may run longer with near-silence after the sound (audible_ms is the sound, duration_ms the file; checks say which was met).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 20, max 50)"New value: +"Max results (default 10, max 50)"
  2. Changed1 schema field changed
    • changedInput schema / properties / max_duration_ms / description
      Previous value: -"Hard maximum delivered duration in milliseconds; format-specific measurement is required."New value: +"Hard maximum length of the sound in milliseconds: a file may run longer with near-silence after the sound (audible_ms is the sound, duration_ms the file; checks say which was met)."
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Keywords or a natural-language description, e.g. 'door slam', 'soft UI confirmation chime', 'coin pickup'"New value: +"Use concise English search terms for the source or event, action and essential audible traits from the user's request or project context: 'door slam', 'soft UI confirmation chime', 'coin pickup'. A single clear source such as 'thunder' is valid; do not pad it. Translate other languages while preserving meaning. Avoid full generation prompts, app backstory, synonym lists and invented materials or environments: full matches must cover every query word. Put duration, loop and format requirements in their separate fields. If no full match exists, inspect closest and missing_terms; simplify only optional wording, never silently drop a required trait."
  4. Changed1 schema field changed
    • changedInput schema / properties / format / description
      Previous value: -"Delivery format (ogg = Ogg Vorbis); loop=true defaults to WAV when omitted."New value: +"Delivery format (ogg = Ogg Vorbis, only sounds published before 2026-10-14 have it); loop=true defaults to WAV when omitted."
  5. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional category slug: ui, retro-game, transition, impact, ambience, water, fire-electric, footsteps, door, mechanical, paper-fabric, glass, animal, crowd, cartoon, magic-scifi, horror, feedback, instrument, office"New value: +"Optional category slug: ui, retro-game, transition, impact, ambience, water, fire-electric, footsteps, door, mechanical, paper-fabric, glass, animal, crowd, cartoon, magic-scifi, horror, feedback, instrument, office, human, vehicle, household"
  6. Changed2 schema fields changed
    • changedInput schema / properties / format / description
      Previous value: -"Delivery format; loop=true defaults to WAV when omitted."New value: +"Delivery format (ogg = Ogg Vorbis); loop=true defaults to WAV when omitted."
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "wav",
-  "mp3"
-]New value: +[
+  "wav",
+  "mp3",
+  "ogg"
+]
  7. Changed3 schema fields changed
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Delivery format; loop=true defaults to WAV when omitted.",
+  "enum": [
+    "wav",
+    "mp3"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / loop
      Added value: +{
+  "description": "Require (true) or exclude (false) a candidate marked with prepared loop metadata; seam evidence is returned separately.",
+  "type": "boolean"
+}
    • addedInput schema / properties / max_duration_ms
      Added value: +{
+  "description": "Hard maximum delivered duration in milliseconds; format-specific measurement is required.",
+  "type": "number"
+}
  8. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already confirm read-only, non-destructive, non-open-world behavior, but the description adds substantial context: fallback to closest matches with missing_terms, library_fit levels, generation options, direct hotlinkable URLs, no API key or attribution, audio measurements, and QC status. No contradiction with annotations is present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and alternatives are front-loaded, but the description is a dense single paragraph packed with output details, fallback behavior, and acoustic metadata. Most content is relevant, but the lack of structure and sheer length make it harder to scan than necessary.

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?

There is no output schema, so the description carries the burden of explaining return values. It does so thoroughly: results vs. closest, missing_terms, library_fit, generation options, direct audio URLs, acoustics, character labels, loop/QC status, and score/match ranking semantics.

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%, so query, loop, limit, format, category, and max_duration_ms are already well documented. The description reinforces that hard constraints always apply and explains fallback matching semantics, but it does not add parameter-specific syntax or constraints beyond the schema.

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?

The description states a specific verb and resource: 'Free-text search over the SFXMint library of free CC0 sound effects.' It explicitly distinguishes this tool from siblings get_role_sound and get_sound_set by naming their different use cases.

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?

It gives explicit when-to-use guidance for sound descriptions, constraints, or gaps, and names alternatives for named events and multi-event tasks. It also explains that these are task branches rather than a fixed sequence, and describes fallback behavior when no full match exists.

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