Skip to main content
Glama

List My Discogs Wantlist

discogs_list_wantlist
Read-only

Lists the owner’s Discogs Wantlist, newest first and paged, so you can check what they want or search by artist/title.

Instructions

List the Wants on the Owner's own Discogs Wantlist: the Releases they want to get.

Use it for "what is on my Wantlist", "do I want anything by X" or "what did I add to my Wantlist recently". Newest first and paged. Each line carries the Release, its Format, label and catalog number, when it was added and the release_id. The query matches artist and title text only: the lines carry no genres or styles, so a query such as "jazz" finds only artists and titles containing the word. Do not use it to find Releases in the catalog (use discogs_search) or to see what the Owner already has (use discogs_list_collection), and use discogs_wantlist_prices for what the Wants cost.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage of Wants, from 1.
limitNoWants per page.
queryNoOnly Wants whose artist or title contain every word of this text, ignoring case, e.g. 'astley'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real behavioral load: result ordering (newest first), pagination, and the exact per-line payload (Release, Format, label, catalog number, date added, release_id). It also discloses a non-obvious search limitation — the query matches artist/title text only, never genres or styles — which no annotation or schema could convey. No output schema exists, and the return shape is described in enough detail that the agent knows what it will get.

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 the core purpose, then usage triggers, then return shape, then exclusions — a sensible order with no filler sentences. Slightly verbose in the result-field enumeration and the parenthetical gloss on 'Wants', but each sentence does carry information an agent needs.

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?

For a read-only, three-parameter list tool with no output schema, the definition covers purpose, triggers, search-semantics limits, return contents, ordering, and sibling routing. An agent could select and call this correctly with no further information.

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%, so baseline is 3, but the description adds meaning beyond the schema by explaining that the query is an all-words, case-insensitive match against artist and title only, and that a term like "jazz" will only hit artists/titles containing it. That semantic caveat is genuinely additive and would change how an agent formulates a query; ordering/paging context also reinforces the page and limit params.

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 with scope: "List the Wants on the Owner's own Discogs Wantlist: the Releases they want to get." The possessive 'Owner's own' immediately separates it from catalog search, and the description explicitly names the siblings it is not (discogs_search, discogs_list_collection, discogs_wantlist_prices).

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 concrete trigger phrases ("what is on my Wantlist", "do I want anything by X", "what did I add recently") plus explicit exclusions with the alternative named for each: discogs_search for catalog, discogs_list_collection for owned items, discogs_wantlist_prices for cost. Nothing is left to inference.

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