Skip to main content
Glama

Sound Cocktail

list_sounds

List all 22 ambient sounds available on Sound Cocktail (12 free, 10 Plus) with their IDs, categories, and free/plus tier.

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

Input Schema

NameRequiredDescriptionDefault
tierNoFilter by free, plus, or all (default: all).
localeNoLanguage for display names (default: en).

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 still conveys that this is a catalog listing operation and discloses the exact total of 22 sounds, the 12 free / 10 Plus split, and the returned fields IDs, categories, and tier. It does not explicitly state read-only behavior, ordering, or authentication requirements, but the 'List' verb strongly implies a safe read operation.

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?

The description is a single front-loaded sentence with no unnecessary wording. It puts the resource and count first, then the returned fields, so every clause earns its place.

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 simple tool with two optional, fully documented parameters and no output schema, the description is largely complete: it states the resource, total count, tier composition, and returned fields. It could still mention that tier and locale act as filters and explicitly confirm read-only behavior, but no critical information is missing.

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 description coverage is 100%, so the schema already documents the tier and locale parameters. The description mentions free/plus tier only as an output attribute, not as a filter parameter, and adds no further parameter meaning beyond 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 states a specific verb and resource: 'List all 22 ambient sounds available on Sound Cocktail.' It also names the exact count, tier split, and returned fields. However, it does not explicitly differentiate this catalog-listing tool from siblings such as recommend_soundscape or build_mix_url.

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 this to browse or retrieve the full ambient sound catalog, optionally filtered by tier. The description does not explicitly say when to use this tool versus recommend_soundscape or build_mix_url, nor does it state exclusions.

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.