Skip to main content
Glama

Get one track

get_track
Read-onlyIdempotent

Get one Uncommon Ear track by id, including its license and terms, attribution status, credit line, source page, preview URL, and page URL.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe track id returned by search_tracks or find_similar.

Output Schema

NameRequiredDescriptionDefault
trackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 closed-world scope, so the safety profile is covered. The description adds that the payload includes licensing and attribution fields, but says nothing about error behavior for unknown ids, rate limits, or auth requirements. With annotations carrying the behavior burden, a 3 is appropriate.

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?

One front-loaded sentence with no padding or hedging. The trailing enumeration of returned fields partly duplicates the existing output schema, which is the only mildly wasteful element.

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?

A one-parameter read tool with full annotation coverage and an output schema needs little prose, and this definition covers purpose and inputs adequately. The field list is redundant given the output schema, and failure modes for an invalid id are unstated, keeping it short of a 5.

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?

There is a single required 'id' parameter at 100% schema coverage, and the schema already states that it is the track id returned by search_tracks or find_similar. The description only repeats 'by id' and adds no format, casing, or validation detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Get one Uncommon Ear track by id') and enumerates what comes back, including license and terms, attribution status, credit line, preview and page URLs. An agent can distinguish this single-record lookup from search_tracks or find_similar without opening a schema.

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 only implied: fetch full details for a track you already have an id for. There is no explicit statement of when to prefer this over search_tracks or find_similar, though the 'by id' framing plus the schema note that ids come from search_tracks or find_similar carries most of the intent.

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