Skip to main content
Glama

Search meme sounds

search_sounds
Read-only

Search DankMachine meme sound buttons by name, alias, tag, mood or use case. Returns playable MP3 URLs, pixel-art images and pages.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_sounds"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodNoOptional mood, e.g. funny, dramatic, awkward, victory, fail, surprise, scary, hype
limitNo
queryYesWords to match, e.g. "vine boom", "dramatic bass", "minecraft"
categoryNoOptional category slug (see list_categories)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 usefully adds the return shape (playable MP3 URLs, pixel-art images, pages), but says nothing about result limits, relevance ranking, or how alias/tag matching behaves, leaving meaningful behavioral gaps.

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 action and resource, followed by the searchable fields and return values. Every clause carries information and there is no filler.

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 read-only search tool with no output schema, the description covers what is searched and what comes back. Minor gaps remain around result limits/relevance and the fact that mood and category are separate filter parameters rather than query terms, but the agent has enough to invoke it correctly.

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 75%, so the baseline is 3, and the description adds real meaning by clarifying that the query matches across name, alias, tag, mood, and use case – broader than the schema's terse 'Words to match'. It does not explain the category parameter beyond the schema's pointer to list_categories, but it compensates for most of the coverage gap.

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 states a specific verb and resource ('Search DankMachine meme sound buttons') and names the searchable dimensions (name, alias, tag, mood, use case). It is clear what the tool does, though it never explicitly contrasts itself with siblings like get_sound or find_reaction_sound, so it falls short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies a text-query search but gives no explicit when-to-use or when-not-to-use guidance and never names an alternative (e.g., get_sound for a known sound, list_categories for browsing). The agent must infer routing from the searchable fields alone.

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.