Skip to main content
Glama

Match Albums Against My Discogs Collection

discogs_match_collection
Read-only

Check albums from another source against a Discogs Collection and Wantlist, returning each as in Collection with release/format, on Wantlist, possible, or absent.

Instructions

Check a list of albums from another source against the Owner's Collection and Wantlist.

Use it for "which of these albums do I have": albums from Last.fm or Spotify listening history, a playlist or a pasted list, up to 200 per call. One line per album: in Collection (with the Release and Format of each matching Copy, so vinyl tells apart from CD), on Wantlist, possible (naming the candidate) or absent. An album is in the Collection when the Owner has any Release of its Master, in any Format; Releases without a Master match on artist and title. Names match ignoring case, diacritics, punctuation, a leading "The", "&" versus "and" and edition qualifiers such as Remastered, Deluxe, Expanded, Anniversary or Mono. A possible match is a Release of the same artist whose title contains the album's title or is contained in it, under another Master; titles that differ only by a series number (III, Vol. 2) are two albums. It reads only the Owner's Collection and Wantlist, never the catalog: do not call discogs_search album by album, and use discogs_list_collection to browse.

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": {
      "albums": "<albums>"
    },
    "name": "discogs_match_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
albumsYes1 to 200 albums as another source names them, e.g. [{"artist": "The Beatles", "title": "Abbey Road (Remastered)"}].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior beyond that: the output shape per album (in Collection / Wantlist / possible / absent), that matches include the Release and Format of each Copy, the Master-vs-Release matching rule, artist/title fallback for Master-less Releases, and the 'possible match' heuristic including the series-number exception (III, Vol. 2 count as two albums). The fuzzy-name normalization rules (case, diacritics, punctuation, leading 'The', '&' vs 'and', edition qualifiers) are disclosed so an agent knows results may vary from literal string comparison.

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?

Front-loaded with purpose, then usage, then output shape, then matching semantics, then exclusions – a sensible order with no filler. It is dense and one sentence is grammatically awkward ('so vinyl tells apart from CD'), but every clause carries decision-relevant information rather than repetition.

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?

There is no output schema, so the description must explain returns – and it does, enumerating the four result categories and the extra Release/Format detail. Combined with the 200-item bound, matching rules, and sibling routing, an agent has everything needed to call this correctly and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents artist/title with examples and the 1–200 bound, so the baseline is 3. The description adds genuine meaning beyond the schema by explaining that input names need not be normalized ('Names match ignoring case, diacritics, punctuation, a leading "The"...'), which changes how an agent should construct and trust the input; it just doesn't elaborate on the per-field object shape.

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?

States a specific verb and resource: 'Check a list of albums from another source against the Owner's Collection and Wantlist.' It also delimits scope against siblings ('It reads only the Owner's Collection and Wantlist, never the catalog'), so an agent can distinguish this match/batch tool from discogs_search and discogs_list_collection without opening either 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?

Gives an explicit use-case phrase ('which of these albums do I have') plus concrete input sources (Last.fm or Spotify history, playlist, pasted list) and a per-call limit of 200. It also names the anti-pattern ('do not call discogs_search album by album') and the correct browsing alternative (discogs_list_collection), which is exactly the routing guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.