Skip to main content
Glama

Find similar tracks

find_similar
Read-onlyIdempotent

Find precomputed same-kind neighbors for a track. An empty list is possible. min_bpm, max_bpm, min_seconds, max_seconds, commercial, credit, and loops_only are post-filters applied before paging; total reflects them.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe track id to use as the starting point.
limitNoNumber of neighbors to return, from 1 to 50.
creditNo
cursorNo
max_bpmNo
min_bpmNo
commercialNo
loops_onlyNo
max_secondsNo
min_secondsNo

Output Schema

NameRequiredDescriptionDefault
totalYes
cursorYes
tracksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, and the description adds real information beyond them: neighbors are precomputed (so results may be stale or absent), an empty result is a legitimate outcome, and the filters are post-filters applied before paging with `total` reflecting them. The only gap is that cursor/paging behavior itself is not described.

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?

Three short sentences, front-loaded with the core behavior, then the empty-result caveat, then the filter/paging semantics. The third sentence is a dense bare list of parameter names but every clause carries information; nothing is filler.

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?

An output schema exists, so the description does not need to explain return values, and the post-filter note covers result-set semantics well. Still, for a 10-parameter tool with a cursor and an unlabeled enum, an agent lacks enough to page correctly or know which credit value to choose.

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 only 20%, so the description has to carry most of the parameter burden. It does add meaning by grouping min_bpm, max_bpm, min_seconds, max_seconds, commercial, credit and loops_only as post-filters applied before paging, which is genuinely useful semantics. However, it leaves `credit`'s enum values ('optional' vs 'requested') and the `cursor` parameter completely unexplained, so it only partially compensates for the coverage gap.

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 gives a specific verb and resource — 'find precomputed same-kind neighbors for a track' — which is far more informative than the title alone and signals a graph/neighbor-style lookup rather than a text search. It implicitly distinguishes itself from search_tracks, but never names similar_to_collection, so the agent must still guess which of the two similarity tools to pick.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing says how this differs from similar_to_collection, or when a plain search_tracks call would be preferable. 'An empty list is possible' is a caveat about outcome, not a condition for selecting the tool.

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