Skip to main content
Glama

Sound Cocktail

build_mix_url

Build a direct playable Sound Cocktail mix URL (https://soundcocktail.app/{locale}/mix/SYL-...) from a map of sound IDs and volumes (0-100).

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": {
      "mix": "<mix>"
    },
    "name": "build_mix_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
mixYesMap of sound IDs (from list_sounds) to volume levels (0-100 or 0.0-1.0), e.g. {"rain": 70, "cafe": 30, "keyboard": 25}.
nameNoShort title for the custom mix (e.g. "Rainy Coding Desk").
localeNoURL language prefix (default: en).

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?

With no annotations, the description carries the full burden, and it does disclose the key behavior: this constructs a URL string rather than playing audio, and the result is 'direct playable' at a known path. It stops short of saying whether sound IDs are validated against list_sounds, what happens on invalid IDs, or that the operation has no side effects.

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 sentence with the output artifact and URL shape front-loaded; no filler, no 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 simple URL-builder with full schema coverage and no output schema, the description is nearly self-sufficient because it inlines the returned URL format. The remaining gap is the lack of any note on how the name and locale parameters surface in the result, or on error behavior for unknown sound IDs.

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 mix, name, and locale, including the enum and the nested map. The description restates the volume range as 0-100 while the schema allows 0-100 or 0.0-1.0, so it adds no new meaning and is marginally narrower than 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?

Names a specific verb (Build) and resource (a playable Sound Cocktail mix URL) and even shows the URL template with the {locale} and SYL- placeholders, so the output is unambiguous. It does not explicitly distinguish itself from list_sounds or recommend_soundscape, which is the only thing keeping it from a 5.

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: the agent can infer this is the tool to call once it already has a sound-to-volume map and needs a shareable link rather than a recommendation or catalog listing. There is no explicit when-to-use, when-not-to-use, or named alternative.

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.