Skip to main content
Glama

ProofProfile evidence (free name search)

find_recording

Read-onlyIdempotent

Discover recordings by artist name, or read one artist's sealed catalogue by artist_id. Supply exactly one of artist or artist_id, optionally title and page. Name search is partial: at most three artist files are read; artistCandidates lists the returned name matches, not necessarily every namesake or only census artists. Show returned recording matches with a brief incomplete-search warning; avoid attributing all matches to one artist without evidence or asking people to pick between indistinguishable IDs. If an artist ID was supplied, use it directly and confirm the selected name and ID. Select an artist_id from those candidates and page through that artist's matching recordings, 25 per page. Release pages are listing context, not proof of a release. Verify the intended recording by ISRC. A name-search miss does not establish absence.

Input Schema

NameRequiredDescriptionDefault
pageNoPage of matching recordings, 25 per page, with or without title
titleNoRecording title, for example The Boys of Summer. Leave it out for all of the artist's recordings.
artistNoArtist name, for example Don Henley
artist_idNoRegistry artist id from artistCandidates or an artist page; use instead of artist

Output Schema

NameRequiredDescriptionDefault
pageNo
@typeYes
genreNo
queryYes
scopeNo
answerYes
statusYes
artistsYes
@contextYes
coverageNo
numberOfItemsNo
numberOfPagesNo
similarArtistsNo
itemListElementNo
artistCandidatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover readOnly/idempotent/closed-world safety; the description goes far beyond them by disclosing that name search is partial (at most three artist files read), that artistCandidates is not an exhaustive namesake list, that release pages are listing context rather than release proof, and that a miss does not establish absence. These are exactly the caveats an agent needs to avoid overclaiming results.

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?

The two operating modes are front-loaded and every clause carries real information about search limits or verification. It is dense and slightly sprawling, with several agent-directed imperatives packed into the middle, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return-value detail is unnecessary, and the description instead supplies the interpretive context that structured fields cannot: partial-search semantics, candidate-list meaning, pagination workflow, and evidence standards. Nothing an agent needs to call or report on this tool correctly appears to be missing.

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%, so artist, artist_id, title, and page are already documented, including the 25-per-page size and the 'use instead of artist' note. The description reinforces the mutual exclusivity and the origin of artist_id (artistCandidates), but adds little syntax or format detail the schema does not already carry, so the baseline of 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?

The first sentence names a specific verb and resource ('Discover recordings') and immediately splits the tool into its two distinct modes: name search versus catalogue read by artist_id. An agent can tell what it retrieves and in which mode without inspecting the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states the selection rule explicitly ('Supply exactly one of artist or artist_id'), prescribes the follow-on workflow (pick an artist_id from artistCandidates, then page through recordings), and gives verification guidance (confirm name and ID, verify by ISRC). It also warns how to present results and what not to infer from a miss, which is genuine when-to-use and how-to-use guidance.

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