Skip to main content
Glama

discogs_database

Read-only

Search Discogs and retrieve artist, label, master, or release details, releases, ratings, and community stats for music catalog research.

Instructions

discogs_database covers the database toolset (11 operations). Token is sent as Authorization: Discogs token= and never in the query string. Local stdio server for one user. Not a hosted service. Actions: get_artist: GET /artists/{artist_id}. Get one artist by id. get_artist_releases: GET /artists/{artist_id}/releases. List releases for an artist. get_label: GET /labels/{label_id}. Get one label by id. get_label_releases: GET /labels/{label_id}/releases. List releases for a label. get_master: GET /masters/{master_id}. Get one master release by id. get_master_versions: GET /masters/{master_id}/versions. List versions of a master release. get_release: GET /releases/{release_id}. Get one release by id. get_release_rating: GET /releases/{release_id}/rating. Get the community rating for a release. get_release_stats: GET /releases/{release_id}/stats. Get community stats for a release (have, want). get_user_release_rating: GET /releases/{release_id}/rating/{username}. Get one user's rating for a release. search: GET /database/search. Search the Discogs database. Requires a token. Anonymous search is refused by Discogs.

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": {
      "action": "<action>"
    },
    "name": "discogs_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON object for writes, or {csv} for inventory uploads. Tokens are redacted in output.
queryNoOpenAPI query parameters, such as page or per_page.
actionYesDiscogs operation to call.
paramsNoOpenAPI path parameters, such as release_id or username.
include_image_urlsNoIf true, keep image URL strings (images, thumb, cover_image, avatar_url). URLs are never fetched. Default false drops those fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description adds genuinely new behavioral context: the token is passed as an 'Authorization: Discogs token=<token>' header and never in the query string, the server is local stdio for a single user rather than a hosted service, and anonymous search is refused. It does not mention rate limiting or pagination behavior for the list operations, so it is not fully exhaustive.

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-loads transport and auth constraints, then presents the 11 operations in a uniform 'action: METHOD path. description.' pattern that scans efficiently. Slight redundancy between the opening token sentence and the 'Requires a token' note on search, and it is long, but for a multiplexed 11-operation tool nearly every line carries information.

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

Completeness4/5

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

For an 11-action multiplexer with no output schema, the description covers action inventory, authentication, and the single-user local-server deployment model, which is what an agent needs to call it safely. Gaps remain around pagination on the list actions and error/rate-limit behavior, but nothing essential to correct invocation 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 goes further by mapping each action to the path parameters it consumes (artist_id, label_id, master_id, release_id, username) via the endpoint templates, which the generic 'params: OpenAPI path parameters, such as release_id or username' schema text does not do per action. It says nothing about the query or include_image_urls parameters, which remain schema-only.

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 the resource scope up front ('database toolset (11 operations)') and then enumerates every action with a specific verb, resource and endpoint (e.g. 'get_release_rating: GET /releases/{release_id}/rating. Get the community rating for a release.'). An agent can map an intent to the correct action without opening the schema, and the catalog-domain focus implicitly separates it from the collection/wantlist/user siblings.

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

Usage Guidelines3/5

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

Usage conditions are only implied by the per-action one-liners; there is no explicit statement of when to choose this tool over discogs_collection, discogs_wantlist or discogs_user. The only hard rule given is a prerequisite ('Requires a token. Anonymous search is refused by Discogs.'), which is auth guidance rather than tool-selection guidance.

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