Skip to main content
Glama

search_track

Read-only

Search the public music catalog by song title and artist. Returns the closest recordings and their ISRC codes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSong title, or "title by artist". You can pass title and artist instead.
titleNoSong title.
artistNoArtist name. Optional.

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 readOnly, non-destructive, open-world access, so the safety profile is covered. The description adds useful context beyond them: that the catalog is public (no auth implied), that matching is fuzzy ('closest recordings'), and what the results contain (ISRC codes). It omits result limits, pagination, and ambiguity handling, so it is not rich.

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?

Two tight sentences with zero waste; the search action is front-loaded and the return value follows immediately.

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 usefully tells the agent what comes back (recordings plus ISRC codes), which is the key missing piece. It falls short on result count, ordering confidence, and ambiguity handling, but is nearly complete for a simple lookup tool.

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 the schema already explains the 'title by artist' shorthand and that artist is optional. The description adds no parameter-level syntax or format guidance, so the baseline 3 applies.

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 ('Search the public music catalog by song title and artist') and specifies the return content (closest recordings and ISRC codes). It does not explicitly distinguish itself from 'isrc_lookup', though the title/artist search framing implicitly separates it from a direct ISRC lookup.

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: an agent can infer this is the tool to use when it has a title/artist rather than an ISRC, but the description never states when to prefer this over 'isrc_lookup' or 'reel_song_info'. No prerequisites or exclusions are given.

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