Skip to main content
Glama

Get Prices of My Discogs Wantlist

discogs_wantlist_prices
Read-only

Checks current Discogs Wantlist marketplace prices, filters Wants at or under a set maximum, and sorts results from cheapest so you can find affordable items.

Instructions

Check what the Wants on the Owner's own Discogs Wantlist cost on the Marketplace now.

Use it for "what on my Wantlist is cheap right now" or "which Wants are under 30 EUR". It checks the Lowest price of at most 30 Wants per call (a page of the Wantlist, newest first), keeps those at or under max_price, sorts them from cheapest and lists the Wants with nothing for sale apart. When more Wants remain, the response says which page to check next. The Lowest price is the cheapest current listing in any condition, excluding shipping: not a market value. There is no price watch: Discogs' own Wantlister sends alerts. Use discogs_get_prices for particular Releases and discogs_list_wantlist to list the Wantlist without prices.

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_wantlist_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of Wants, from 1.
limitNoWants checked per call, newest first; at most 30.
queryNoOnly Wants whose artist or title contain every word of this text, ignoring case, e.g. 'astley'.
currencyNoCurrency of the prices; EUR by default.
max_priceNoOnly Wants whose Lowest price is at or under this amount, in the currency of the call, e.g. 30. Wants for sale above it are only counted.

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 context beyond that: a 30-Want page cap, newest-first ordering, filtering by max_price, cheapest-first sorting, Wants with no listings listed separately, and a next-page hint in the response. It also defines 'Lowest price' as the cheapest current listing in any condition excluding shipping and warns that this is not market value.

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?

Purpose is front-loaded and the use cases and alternatives follow in a logical order with no filler. It is dense and slightly run-on, and the '(a page of the Wantlist, newest first)' parenthetical partly duplicates the limit parameter's schema text.

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?

Despite having no output schema, the description covers what comes back (sorted Wants, unsold Wants separated, next-page indicator) plus the meaning and limits of the price data. Nothing an agent needs to call this correctly or interpret the result is missing.

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 the baseline is 3, but the description adds real meaning: it explains that max_price filtering counts rather than drops over-threshold Wants, and that page/limit operate on a newest-first 30-item window. The currency default of EUR merely restates the schema, so it falls short of a 5.

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: it checks what the Wants on the Owner's own Discogs Wantlist cost on the Marketplace now. It also implicitly separates itself from discogs_get_prices (particular Releases) and discogs_list_wantlist (no prices), so an agent can pick it without opening another 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 concrete triggering questions ('what on my Wantlist is cheap right now', 'which Wants are under 30 EUR') and explicitly names two alternatives with the condition that selects them. It also rules out a misuse case (no price watch; use Discogs' Wantlister for alerts).

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