Skip to main content
Glama

Get a track

get_track
Read-onlyIdempotent

Get a track by cue_id: name, preview URL, length, bpm, key, style and sections.

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": {
      "cue_id": "<cue_id>"
    },
    "name": "get_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
cue_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description's only addition is a list of returned fields, which duplicates the output schema rather than adding behavioral context such as not-found handling or data freshness. No contradiction with annotations.

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 with the action and lookup key front-loaded and zero filler. Nothing is redundant or padded.

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?

For a one-parameter read tool with an output schema and full annotations, the definition covers what is needed to invoke it correctly; return values are already documented elsewhere. The only gap is edge-case behavior when the cue_id does not resolve to a track.

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 0% for the single parameter, so the description carries the burden. It clarifies that cue_id is the track identifier used for lookup, which is real added meaning, but gives no format, source, or validity constraints for the value.

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 verb and resource ("Get a track") plus the lookup key (cue_id) and the fields returned, so the agent knows this is a single-item retrieval rather than a search. It does not explicitly name a sibling like find_tracks, but the "by cue_id" scoping makes the distinction inferable.

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?

The phrase "by cue_id" implies this tool is for fetching one known track, contrasting implicitly with search-style siblings such as find_tracks. There is no explicit when-to-use/when-not-to-use statement, no mention of what happens when the cue_id is unknown, and no guidance on prerequisites.

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.