Skip to main content
Glama

Discogs Get Artist

discogs_get_artist
Read-onlyIdempotent

Fetch a Discogs artist profile by artist_id. Returns name, real name, profile bio, URLs, aliases, group memberships, images, and Discogs URL.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "artist_id": 125959
    },
    "name": "discogs_get_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
artist_idYesDiscogs artist ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is covered structurally. The description adds the payload contents (bio, aliases, group memberships, images) but says nothing about rate limiting, authentication, or what happens on an unknown artist_id, which for an open-world external API lookup would be genuinely useful.

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?

Two tight sentences with the action front-loaded and no filler. The second sentence's field enumeration is slightly redundant against the output schema but earns its place as a quick relevance check for the agent.

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 single-parameter lookup with full schema coverage, an output schema, and complete annotations, the definition is nearly complete. What's missing is only edge-case behavior (invalid/nonexistent artist IDs) and the pointer to discogs_search for discovering IDs.

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% for the single artist_id parameter, so the baseline of 3 applies. The description mentions 'by artist_id' but adds no format guidance beyond the schema's 'Discogs artist ID' — for example, no note on where to obtain the ID or that numeric Discogs IDs differ from MusicBrainz IDs.

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 gives a specific verb and resource — 'Fetch a Discogs artist profile by artist_id' — and enumerates the returned fields, making the entity type (artist, not release/label/master) unmistakable. It does not explicitly name a sibling, but the resource noun alone separates it from the release/label/master tools in the catalog.

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 is only implied: the phrase 'by artist_id' signals that a numeric Discogs artist ID is a prerequisite, hinting an agent may need discogs_search first, but that is never stated. There are no exclusions, no when-not-to-use, and no explicit routing to alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.