Skip to main content
Glama

discogs_wantlist

DestructiveIdempotent

Manage a Discogs wantlist by adding, removing, listing, or updating releases with notes and ratings; writes require confirmation and can preview as a dry run.

Instructions

discogs_wantlist covers the wantlist toolset (4 operations). Token is sent as Authorization: Discogs token= and never in the query string. Local stdio server for one user. Not a hosted service. Writes need confirm set to the boolean true and DISCOGS_ALLOW_WRITES=true. Omit confirm for a dry-run preview that does not send the request. Actions: add: POST /users/{username}/wants/{release_id}. Add a release to the wantlist. delete: DELETE /users/{username}/wants/{release_id}. Remove a release from the wantlist. Warning: This removes a release from the wantlist. list: GET /users/{username}/wants. List the user's wantlist. update: PUT /users/{username}/wants/{release_id}. Add or update a wantlist item (notes, rating).

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

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.
confirmNoSet to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.
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
Behavior5/5

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

Beyond annotations, the description discloses the auth scheme (header token, never query string), that this is a single-user local stdio server rather than a hosted service, the write-gating requirements, and that omitting confirm yields a dry-run that sends nothing. It also flags the destructive consequence of 'delete' on the wantlist, which is exactly the kind of context annotations alone cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the important operational constraints and uses a clean action list, but the dry-run rule is stated twice (once in the preface and again implicitly in the confirm discussion) and the endpoint paths plus prose descriptions are somewhat redundant for each action.

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 a 4-operation, 6-parameter mutation tool with no output schema, the description covers auth, deployment model, write safety gating, dry-run behavior, and per-action semantics. What remains thin is what 'list' returns and pagination behavior, which is left entirely to the query schema.

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 would be 3, but the description adds real meaning to confirm (must be boolean true; false and the string 'true' are rejected; omission means dry-run) and maps params to concrete path variables such as username and release_id. It says less about body/query/include_image_urls, which the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (wantlist) and enumerates all four operations with their HTTP verbs and paths, so an agent knows exactly what 'add', 'delete', 'list' and 'update' do here. It does not explicitly contrast itself with siblings like discogs_collection or discogs_user, so sibling differentiation is only implicit in the resource name.

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

Usage Guidelines4/5

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

Each action carries a one-line when-to-use statement ('Add a release to the wantlist', 'Remove a release from the wantlist'), and the write path is gated with concrete conditions (confirm=true plus DISCOGS_ALLOW_WRITES=true). No explicit when-not-to-use guidance relative to sibling toolsets is given.

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