Skip to main content
Glama

discogs_user

Retrieve and edit a Discogs user profile, view token identity, and list contributions or submissions, with confirmed writes and dry-run previews.

Instructions

discogs_user covers the user toolset (5 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: edit_profile: POST /users/{username}. Edit the authenticated user's profile. get_identity: GET /oauth/identity. Return the identity of the authenticated token holder. get_profile: GET /users/{username}. Get a user profile. Profile HTML/BBCode is requested as plaintext. list_contributions: GET /users/{username}/contributions. List a user's contributions. list_submissions: GET /users/{username}/submissions. List a user's submissions.

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

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.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false; the description adds real substance on top: the auth header format, the environment-level write gate, the dry-run-by-omission semantics, and that profile HTML/BBCode is returned as plaintext. That is precisely the kind of operational context the annotations cannot convey, and nothing conflicts with them.

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?

Transport and write-gating constraints are front-loaded before the action catalog, which is the right order for an agent deciding whether it can call at all. The prose is dense and slightly run-on (auth, hosting model, write gating and dry-run packed into consecutive sentences), but each sentence carries information rather than filler.

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 six-parameter tool with nested objects and no output schema, the definition covers auth, write safety, dry-run behavior and per-action semantics well. The remaining gap is return-shape detail: actions are summarized in one line each ('List a user's contributions') with no note on pagination or result envelope, which an agent must discover empirically via query params.

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 the schema already documents body, query, params, confirm and include_image_urls in detail. The description's confirm guidance largely restates the schema's own wording, and its only genuine addition is hinting that path parameters are things like username/release_id via the endpoint templates. Baseline 3 is appropriate when the schema carries this much.

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?

The description names the resource scope (user toolset, 5 operations) and then enumerates each action with a specific verb, resource and HTTP endpoint: edit_profile POST /users/{username}, get_identity GET /oauth/identity, get_profile, list_contributions, list_submissions. An agent can map each enum value to a concrete operation without inspecting the schema, and the user-centric scope distinguishes it from collection/lists/wantlist siblings.

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?

Conditional guidance for writes is explicit: confirm must be the boolean true and DISCOGS_ALLOW_WRITES=true, and omitting confirm yields a dry-run preview that sends nothing. It also states the token travels in the Authorization header, never the query string, and that the server is local stdio rather than hosted. It stops short of explicitly naming when to prefer a sibling (e.g. discogs_collection) over list_contributions, which keeps it at 4.

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