Skip to main content
Glama

find_similar

Find AINSOF cues that sound like an AINSOF cue — the whole cue, or a passage of it marked with from and to (seconds, 5–60 s long), e.g. the hook or the bar before the drop. Each result names the matching passage inside it. Takes a track_id or the cue's title. For a song by another artist (a YouTube, Spotify, Apple Music or Deezer link) use search_by_reference instead.

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": {
      "track_id": "<track_id>"
    },
    "name": "find_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the marked passage, in seconds (5–60 s after from).
fromNoStart of the marked passage, in seconds. Omit for the whole cue.
top_kNo
track_idYese.g. 'AIN-CAT 030_001' or 'Along The River'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / top_k / default
      Previous value: -8New value: +15
  2. Changed1 schema field changed
    • changedInput schema / properties / top_k / default
      Previous value: -10New value: +8
  3. Added

TDQS

A4.3/5.0
Behavior3/5

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

The annotations already declare the safety profile (destructiveHint=false, openWorldHint=false) and oddly readOnlyHint=false, and the description adds real context: the 5–60 s passage constraint and that each result names the matching passage within it. However, it does not explain what the results contain beyond that, how results are ordered, or why the operation is flagged as non-read-only. It adds value without fully covering behavior beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose and the passage constraint, then the alternate tool routing — good ordering with no filler sentences. The parenthetical asides make it dense but every clause carries information.

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?

No output schema exists, yet the description covers the key return characteristic (each result names the matching passage inside it) and the input modes. For a 4-parameter similarity search with annotations present, this is nearly complete; a note on result ordering or limits would close the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, and the description still adds meaning: it explains that from/to mark a passage in seconds and are 5–60 s long, that omitting from means the whole cue, and that track_id may be an ID or a title. top_k is left entirely to the schema, which is a minor gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find AINSOF cues that sound like an AINSOF cue') and narrows it to two modes: the whole cue or a marked passage. It explicitly names the sibling that covers a different case ('For a song by another artist ... use search_by_reference'), so an agent can distinguish it without opening the other schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives concrete when-to-use guidance (whole cue vs. passage such as 'the hook or the bar before the drop') and an explicit exclusion that routes external-artist links to search_by_reference. It also names the accepted identifiers (track_id or the cue's title), leaving little to inference.

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