Skip to main content
Glama

PickTrack — DJ charts

Find harmonically compatible tracks

find_compatible_tracks
Read-onlyIdempotent

Chart tracks that mix harmonically with a given Camelot key (same key, ±1 on the wheel, or relative major/minor) and a similar BPM — for building a DJ set.

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": {
      "camelot": "<camelot>",
      "bpm": "<bpm>"
    },
    "name": "find_compatible_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
bpmYesTempo of the current track.
genreNoOptional: only this genre. Chart genre slug. house = House; tech_house = Tech House; deep_house = Deep House; afro_house = Afro House; melodic_techno = Melodic Techno; techno = Techno/Rave; indie_dance = Indie Dance; amapiano = Amapiano; drum_and_bass = Drum & Bass; uk_garage = UK Garage / Speed Garage; dubstep = Dubstep; rnb = R&B; regional = Arabic Afro House; kpop = K-Pop; psy_trance = Psy-Trance; lo_fi = Lo-Fi / Chill Hop; top50 = Top 50 (all genres)
camelotYesCamelot key of the current track, e.g. 8A.
bpm_rangeNoAllowed BPM difference (default 3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / genre / description
      Previous value: -"Optional: only this genre. Chart genre slug. house = House; tech_house = Tech House; deep_house = Deep House; afro_house = Afro House; melodic_techno = Melodic Techno; techno = Melodic House / Rave / Techno; indie_dance = Indie Dance; amapiano = Amapiano; drum_and_bass = Drum & Bass; uk_garage = UK Garage / Speed Garage; dubstep = Dubstep; rnb = R&B; regional = Arabic Afro House; kpop = K-Pop; psy_trance = Psy-Trance; lo_fi = Lo-Fi / Chill Hop; top50 = Top 50 (all genres)"New value: +"Optional: only this genre. Chart genre slug. house = House; tech_house = Tech House; deep_house = Deep House; afro_house = Afro House; melodic_techno = Melodic Techno; techno = Techno/Rave; indie_dance = Indie Dance; amapiano = Amapiano; drum_and_bass = Drum & Bass; uk_garage = UK Garage / Speed Garage; dubstep = Dubstep; rnb = R&B; regional = Arabic Afro House; kpop = K-Pop; psy_trance = Psy-Trance; lo_fi = Lo-Fi / Chill Hop; top50 = Top 50 (all genres)"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add behavior — and it does, spelling out the harmonic matching rule (same key, ±1 on the wheel, or relative major/minor) that determines what comes back. It does not mention result limits, ordering, or ranking, which is the remaining gap.

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, front-loaded with the verb and the matching rule, with the use case appended. Nothing is redundant and nothing essential is buried.

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?

With four fully documented parameters, rich annotations, and no output schema, the description covers what an agent needs to invoke the tool correctly. The only unstated element is the shape of the returned list (size, ordering), a minor omission for a read-only search.

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%, including the default for bpm_range and the Camelot pattern, so the schema already carries parameter meaning. The description adds only the framing that bpm/bpm_range express 'similar BPM' tolerance and camelot drives harmonic matching — useful but marginal, matching the baseline of 3.

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 ('Chart tracks') plus the exact selection criteria (harmonic key match and similar BPM), so an agent immediately knows this is a compatibility-based track search rather than a plain lookup like find_track or a chart fetch like get_chart. It stops short of explicitly contrasting itself with those siblings, which keeps 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 Guidelines4/5

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

'For building a DJ set' supplies a clear situational context that tells the agent when this tool is the right pick. There are no explicit exclusions or named alternatives for cases where the agent just wants a single track by name, so it lands at clear-context-but-no-routing rather than a full 5.

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