Skip to main content
Glama

Browse candidate sounds with full meme context

browse_sounds
Read-only

Get up to 50 candidate sounds with everything known about each one: about, origin (where the meme comes from, only when known), how_used (how people use it), variations, moods, use_cases, good_for platforms, tags and popularity. Filter by mood, use_case, category or platform (see list_filters), optionally narrow with a query, then choose the best sound yourself.

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

Input Schema

NameRequiredDescriptionDefault
moodNo
limitNo
queryNoOptional words to match
categoryNo
platformNotiktok, youtube, instagram-reels, capcut, discord, twitch, obs, zoom, video-editing, group-chats
use_caseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond them by capping results at 50 and warning that origin is returned 'only when known', which signals nullable data. It says nothing about ordering, relevance ranking, or what happens when no sounds match.

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?

Two sentences, front-loaded with the result size and contents, then the filtering path. The long field enumeration is dense but each item is informative rather than filler; minor tightening would still be possible.

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?

With no output schema, the description correctly takes on the job of enumerating returned fields (about, origin, how_used, variations, moods, use_cases, good_for, tags, popularity), which is exactly what an agent needs to judge suitability. Gaps remain around result ordering and empty-result behaviour, but the core is well covered for a zero-required-parameter list tool.

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 only 33%, so the description must carry weight, and it does: it names mood, use_case, category, platform and query and explains that the query is an optional narrowing step, and it points to list_filters for valid filter values rather than leaving them opaque. The limit parameter's default and range are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Get up to 50 candidate sounds') plus the scope of returned fields, so an agent knows exactly what it retrieves. It does not explicitly contrast itself with the sibling search_sounds, whose name suggests overlapping behaviour, so sibling differentiation is only partial.

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?

It describes a clear usage flow: filter by mood/use_case/category/platform, optionally narrow with a query, then pick the best sound yourself. It also routes the agent to list_filters for valid filter values. It lacks explicit exclusions ('use X instead when'), which keeps it below a 5.

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.