Skip to main content
Glama

Get Discogs Marketplace Prices

discogs_get_prices
Read-only

Compare current Discogs Marketplace prices for up to 10 releases, showing each lowest listing, available copies, sale status, and report time.

Instructions

Show what Releases (pressings) cost on the Discogs Marketplace right now.

For each of 1 to 10 release_ids: the Lowest price, how many copies are for sale and whether the Release is blocked from sale, with the time Discogs reported it. The Lowest price is the cheapest current listing in any condition, excluding shipping: not a market value. Use it to compare editions by price, for example after discogs_list_master_releases. For the prices of the Owner's Wantlist use discogs_wantlist_prices.

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": {
      "release_ids": "<release_ids>"
    },
    "name": "discogs_get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoCurrency of the prices; EUR by default.
release_idsYes1 to 10 Discogs release_ids, e.g. [249504].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare readOnlyHint and openWorldHint, so safety is covered; the description goes further by defining what the returned numbers actually mean — cheapest current listing in any condition, excluding shipping, explicitly 'not a market value' — and enumerates the per-release payload (lowest price, copies for sale, blocked status, report time). For a tool with no output schema, that semantic framing is exactly the value the description should add.

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 price definition and the sibling routing are front-loaded and each sentence carries information an agent needs. It is slightly dense, packing return fields, a caveat, a use case, and a redirect into one block, but nothing is padding.

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, two-parameter lookup with no output schema, the description covers the payload shape, the meaning of the headline value, the batch size, and the alternative tool. Nothing an agent needs in order to call this correctly and interpret the result is 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 both parameters are already documented, and the description only restates the 1-to-10 release_ids bound ('For each of 1 to 10 release_ids') without adding format or edge-case guidance. The currency parameter, including its EUR default and the enum list, is never mentioned in prose, so the baseline 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?

Opens with a specific verb and resource: 'Show what Releases (pressings) cost on the Discogs Marketplace right now.' It immediately names the sibling it is not (discogs_wantlist_prices) and previews the return fields, so an agent can distinguish it from price-adjacent siblings without opening a 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 ('compare editions by price, for example after discogs_list_master_releases') and an explicit alternative with its selection condition ('For the prices of the Owner's Wantlist use discogs_wantlist_prices'). Both when-to-use and when-not-to-use are stated, not inferred.

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