Skip to main content
Glama
Hermoso

Hermoso

Official

Find a sound

find_sound

Locate an edit sound by name, moment, meaning, or link and return a durable MP3 with start and end points, plus alternate candidates.

Instructions

A sound for an edit by name ('the FAAAA sound'), by the moment ('bad news reaction') or by link (TikTok sound, meme-sound page, post, audio file): a durable mp3 and where it starts and lands. Named/described sounds come from what TikTok uses now; pick takes another candidate. A sound that does not exist yet is generate_sfx.

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

Input Schema

NameRequiredDescriptionDefault
urlNolink to a TikTok sound, a post, a meme-sound page or an audio file
pickNocandidate number from the previous list to take instead of the first
queryNosound by name, moment or meaning, e.g. 'bad news reaction'
get_costNotrue: return the price only; nothing runs or bills
idempotency_keyNochosen once, resent unchanged on retries: the same key never buys twice
expected_creditsNothe get_cost price; refused unbilled if the live price differs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.532
    • addedInput schema / properties / expected_credits
      Added value: +{
      +  "description": "the get_cost price; refused unbilled if the live price differs",
      +  "type": "number"
      +}
    • addedInput schema / properties / get_cost
      Added value: +{
      +  "description": "true: return the price only; nothing runs or bills",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "chosen once, resent unchanged on retries: the same key never buys twice",
      +  "type": "string"
      +}
  2. Changed3 schema fields changedv0.1.465
    • addedInput schema / properties / pick / description
      Added value: +"candidate number from the previous list to take instead of the first"
    • addedInput schema / properties / query / description
      Added value: +"sound by name, moment or meaning, e.g. 'bad news reaction'"
    • addedInput schema / properties / url / description
      Added value: +"link to a TikTok sound, a post, a meme-sound page or an audio file"
  3. Addedv0.1.285

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already flag openWorldHint and destructiveHint=false; the description adds the useful non-annotated fact that results are durable mp3s with start/land timing. However, it says nothing about the paid nature of the call — get_cost, expected_credits and idempotency_key imply billing and retry semantics that an agent should know before invoking. With readOnlyHint=false the operation is not a pure read, and the description never explains what is charged or that a repeat with the same key will not re-buy.

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, front-loaded with the resource and enumeration of input modes, followed by what is returned and the sibling escape hatch. Parenthetical examples do real work by showing the intended query phrasing rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly carries the return format (durable mp3 plus start/land positions). But for a tool that can spend credits and is annotated non-idempotent, omitting any mention of cost preview, billing, or retry safety leaves a real gap relative to its complexity.

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%, so the schema already documents all six parameters, including the cost and idempotency mechanics. The description adds only marginal meaning beyond that — clarifying that 'pick' selects an alternative from a previously returned candidate list. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names the resource (a sound for an edit) and the three resolution modes: by name ('the FAAAA sound'), by moment ('bad news reaction'), or by link (TikTok sound, meme page, post, audio file). It also states the payoff — 'a durable mp3 and where it starts and lands' — which no sibling offers. The verb is implicit rather than stated up front, which keeps it just short of 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 Guidelines4/5

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

It gives a clear routing rule to the alternative: 'A sound that does not exist yet is generate_sfx.' It also explains the 'pick another candidate' path when a prior list exists and notes that named/described sounds come from current TikTok usage. There is no explicit when-not guidance for link inputs versus query inputs, but the modes are self-selecting.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools