Skip to main content
Glama

PickTrack — DJ charts

Get a genre chart

get_chart
Read-onlyIdempotent

Current monthly PickTrack chart for one genre: the Top 3 tracks with artist, BPM, Camelot key, release date and SoundCloud link, plus the BPM/key of the next locked ranks and a link to the full chart.

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": {
      "genre": "<genre>"
    },
    "name": "get_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNotop100 = most engaged tracks this month (default). hot100 = the next 100, fast risers.
genreYesChart 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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / genre / description
      Previous value: -"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: +"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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. On top of that, the description discloses the exact shape of the result (Top 3 only, which fields, the BPM/key of the next locked ranks, and a link to the full chart) – meaningful context that tells the agent the response is a preview, not the whole chart. That 'Top 3 preview' framing is the kind of caveat annotations cannot express.

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?

A single front-loaded sentence that establishes tool, scope and freshness before enumerating the returned fields. It is dense but every clause carries information; only the field laundry-list is slightly compressed.

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 no output schema, the description carries the full burden of explaining returns and does so concretely, including the truncation to Top 3 and the pointer to the full chart. It falls short only in not helping the agent choose between this and get_charts_overview for broader chart needs.

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% and both enum parameters are fully documented in the schema, so the baseline of 3 applies. The description only echoes that a chart is for "one genre" and does not clarify the list=top100 vs hot100 distinction or how 'next locked ranks' relates to that parameter, adding little beyond 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?

States a specific resource and scope: "Current monthly PickTrack chart for one genre," with a concrete payload description (Top 3 tracks with artist, BPM, Camelot key, release date, SoundCloud link). It is unmistakably a single-genre chart read, but it never distinguishes itself from get_charts_overview, so a sibling choice still requires inference.

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 implied by "for one genre" and "Current monthly" – an agent can infer this is the right tool when it wants one genre's current chart. However, there is no explicit when-to-use statement, no exclusions, and no named alternative (get_charts_overview, find_track) to route against.

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