Skip to main content
Glama

Find a reaction sound for a situation

find_reaction_sound
Read-only

Describe a moment ("my code finally compiled", "awkward silence", "plot twist") and get candidate meme sounds with their full culture (origin, how_used, moods, use_cases, good_for platforms). Read them and pick the one that fits best yourself.

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": {
      "situation": "<situation>"
    },
    "name": "find_reaction_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
situationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / default
      Previous value: -5New value: +10
    • changedInput schema / properties / limit / maximum
      Previous value: -10New value: +25
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world behavior. The description adds real value beyond them: it discloses what is returned (origin, how_used, moods, use_cases, good_for platforms), how many candidates come back, and the crucial expectation that the agent must evaluate results and pick one itself.

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 core action and followed by the result shape and the selection expectation. The parenthetical field list is dense but informative; every element earns its place and nothing is 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 two-parameter read-only tool, the description covers input style, output fields, and the post-call workflow, which is enough to invoke it correctly without an output schema. The main gap is the undocumented limit parameter.

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 coverage is 0%, so the description must compensate. It explains the situation parameter well with three concrete examples of the expected free-text style, but says nothing about the limit parameter, which is bounded 1-25 with a default of 10 – an agent would not know it controls candidate count.

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 action (describe a moment, get candidate meme sounds) with concrete examples of input, and it distinguishes itself implicitly from get_random_sound/get_sound by emphasizing situational matching. It lacks an explicit contrast with the sibling search_sounds, which appears closest.

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

Usage Guidelines3/5

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

Usage is implied: use when you have a described moment rather than a known sound name or category. No explicit when-not guidance or naming of alternatives (e.g., use search_sounds for keyword lookups, browse_sounds for browsing) is given, so the agent must infer routing.

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.