Skip to main content
Glama

PickTrack — DJ charts

Find a track in the charts

find_track
Read-onlyIdempotent

Look up a track or artist in this month's PickTrack charts: which genre chart it is in, its rank, BPM and Camelot key.

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": {
      "query": "<query>"
    },
    "name": "find_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTrack title and/or artist name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the safety profile is covered. The description adds the useful scope constraint that only the current month's charts are searched, plus the exact fields returned. It omits what happens on a miss (empty result vs. error) or ambiguous artist names, which matters for a name-based lookup.

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?

One sentence, front-loaded with the action and scope, then the returned fields. No filler or redundancy; 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?

With no output schema, the description compensates by naming the return fields, which is exactly what an agent needs to decide whether this tool answers its question. The remaining gap is match/miss behavior and the currency of the data (is it a snapshot of this month only?), minor for a simple read-only lookup.

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% and there is a single parameter, so baseline is 3. The description's "track or artist" usefully signals that the query accepts either or both, a slight extension over the schema's "Track title and/or artist name" but nothing about matching semantics (exact vs. fuzzy, partial titles).

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+resource ("look up a track or artist") scoped to "this month's PickTrack charts" and even enumerates what comes back (genre chart, rank, BPM, Camelot key). That is well beyond a restatement of the name. It stops short of explicitly differentiating itself from siblings like get_chart or find_compatible_tracks, so the sibling split is left to 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 rather than stated: the phrase "this month's PickTrack charts" tells an agent the tool is for current chart membership and not historical data or compatibility lookup. There is no explicit when-to-use vs. get_chart/get_charts_overview guidance and no stated exclusions.

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