Skip to main content
Glama

get_sound

Get one Bencho sound as code: a small TypeScript file that plays it with the Web Audio API (no audio files, no packages), the same synthesis bencho.dev uses, plus how to call it.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe sound id, from search_sounds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses that the output is executable TypeScript source rather than audio data, that it has no external dependencies ('no audio files, no packages'), and that it includes call instructions. It omits failure behavior for an unknown or invalid id, which is the main remaining gap for a read 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?

One front-loaded sentence leads with the action and resource, then immediately clarifies what 'as code' means with the parenthetical. Every clause contributes information and nothing is redundant.

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 getter with no output schema, the description compensates well by explaining the returned artifact and its self-contained nature. Only error/not-found behavior is left out, which is a minor omission rather than a blocking gap.

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?

There is a single required parameter at 100% schema coverage, where the schema already states it is 'The sound id, from search_sounds.' The description adds no further meaning about id format, validity, or expected values, so the baseline 3 applies.

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 uses a concrete verb+resource ('Get one Bencho sound as code') and specifies the return form: a small TypeScript file using the Web Audio API. The singular 'one' plus the id-based retrieval implicitly separates it from search_sounds, but no sibling is named explicitly, so it stops just short of full differentiation.

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: an agent can infer this is the retrieval step after search_sounds has supplied an id. There is no stated when-to-use vs when-not, no mention of alternatives, and no prerequisites described in the definition itself.

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