Skip to main content
Glama

sounds

by com.sfxmint
OverviewDiscussionsAdmin

search_sounds

Free-text search over 4,600+ 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. Exact keyword matches come first, then semantic nearest neighbours; hard constraints are applied before the result limit and a request may validly return no qualified candidate with near-match diagnostics. Returns direct, hotlinkable MP3/WAV URLs and verified OGG (Vorbis) URLs where available — no API key, no attribution required — plus measured acoustics (attack_ms, tail_ms, centroid_hz), 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

TableJSON Schema
NameRequiredDescriptionDefault
loopNoRequire (true) or exclude (false) a candidate marked with prepared loop metadata; seam evidence is returned separately.
limitNoMax results (default 20, max 50)
queryYesKeywords or a natural-language description, e.g. 'door slam', 'soft UI confirmation chime', 'coin pickup'
formatNoDelivery format (ogg = Ogg Vorbis); 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
max_duration_msNoHard maximum delivered duration in milliseconds; format-specific measurement is required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. 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"
+}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it excels: it discloses search ordering (exact keyword matches first, then semantic nearest neighbours), constraint application before the result limit, the possibility of no qualified candidate, return details (direct URLs, acoustics, character labels, loop/QC status), and the meaning of score/match fields. This is comprehensive behavioral transparency.

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?

The description is dense but every sentence earns its place: purpose, usage, alternatives, search mechanics, constraints, return data, and ranking labels are all covered without redundancy. It is longer than average, but the tool's complexity justifies it. Front-loading the purpose and usage guidelines ensures the agent quickly grasps the core.

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?

The description is complete for a search tool with no output schema: it explains what the return contains (URLs, acoustics, labels, QC status, ranking evidence) and how to interpret the match types (role, exact, partial, semantic). It also covers constraints and edge cases. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so the schema already documents all six parameters. The description adds value by explaining cross-parameter behavior: 'loop=true defaults to WAV when omitted,' 'hard constraints are applied before the result limit,' and 'max_duration_ms' being a hard maximum with format-specific measurement. It also clarifies the ranking semantics tied to the query parameter. This exceeds the baseline 3.

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 opens with a specific verb and resource: 'Free-text search over 4,600+ free CC0 sound effects.' It explicitly differentiates from siblings by naming alternatives and the conditions to choose them: 'Choose get_role_sound for a named event or get_sound_set for multiple events when that fits the task.' This makes the tool's purpose unambiguous and distinct.

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?

The description clearly states when to use this tool: 'Use it for sound descriptions, additional constraints or gaps left by another tool.' It also explains the relationship with siblings: 'these are task branches, not a fixed sequence.' Additionally, it notes that requests may return no qualified candidate with diagnostics, setting expectations for edge cases.

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