Skip to main content
Glama

search_sounds

Find Bencho UI sounds — short interface sound effects synthesised in the browser (clicks, toggles, pops, swipes, notifications, progress) — by name, feel or use, e.g. 'soft click', 'success', 'toggle off'. Returns ids to pass to get_sound.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (default 10, max 30).
queryNoWhat you are looking for, in plain words.
categoryNoOptional: Actions, Feedback, Navigation, Notifications, Selection, Movement, Progress or System.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that results are ids rather than audio and that sounds are browser-synthesised, but says nothing about matching behavior (fuzzy vs exact), what an empty result looks like, or whether omitting query browses everything. Adequate but with real gaps for a zero-annotation tool.

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

Conciseness5/5

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

Two sentences, front-loaded with the verb and resource, with the domain enumeration and the downstream handoff to get_sound packed in without filler. Every clause carries information.

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 three-parameter, no-output-schema search tool, the description covers what it returns (ids) and the next step, which is the key missing piece an agent would otherwise lack. It leaves open the no-query browse case and category semantics, but nothing essential to a correct first call is absent.

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, and the description earns an extra point by giving concrete query examples ('soft click', 'success', 'toggle off') that clarify the intended free-text style beyond the schema's generic 'in plain words'. It does not elaborate on category or limit, but the schema already handles those.

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 ('Find Bencho UI sounds'), enumerates the domain (clicks, toggles, pops, swipes, notifications, progress), and distinguishes itself from the sibling get_sound by noting it returns ids to pass there. An agent can tell search from fetch without opening either schema.

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?

The closing clause 'Returns ids to pass to get_sound' establishes the search-then-fetch workflow, and the query examples ('soft click', 'success', 'toggle off') show what kinds of inputs are appropriate. It stops short of explicit exclusions, e.g. whether to use this versus list_categories for browsing, but the context is clear.

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