Skip to main content
Glama

Get one sound

get_sound
Read-only

Full metadata for one sound by slug (or the best match for a query).

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": {
      "sound": "<sound>"
    },
    "name": "get_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
soundYesSlug like "vine-boom-sound-70972" or a search query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 by structured data. The description adds one genuinely useful behavioral fact that the schema does not: a non-slug query is tolerated and resolved to a best match rather than failing. It omits what happens on zero matches (error, null, empty) and what 'full metadata' contains.

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?

A single tight sentence with the resource first and the input-mode caveat in parentheses. No filler, no redundant restatement of the title.

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 one-parameter read-only lookup with no output schema, this covers the essentials: what it returns (full metadata), how to identify the sound, and the fuzzy-match behavior. The only gap is the not-found case, which matters because the query mode can miss.

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 100% and the parameter's own description already spells out the slug format and query fallback, so the description largely restates it. Baseline 3 applies since the schema does the heavy lifting; the only added nuance is the 'best match' resolution semantics.

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?

States a specific verb+resource ("Full metadata for one sound") and names the two accepted input modes: slug or query. It distinguishes itself from search/list siblings by scoping to a single retrieved record, though it never names those siblings for contrast.

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 only implied: fetch a known sound by slug, or pass a query to get the best match. There is no explicit guidance on when to prefer search_sounds or find_reaction_sound instead, nor on what to do if the best match is wrong.

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.