Skip to main content
Glama
cswkim

Discogs MCP Server

by cswkim

get_artist

Retrieve detailed artist information from the Discogs music database by providing a specific artist ID for catalog management and research.

Instructions

Get an artist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
artist_idYes

Implementation Reference

  • Defines the MCP 'get_artist' tool, including its handler (execute function) that fetches artist data using ArtistService.get(args) and returns JSON.
    export const getArtistTool: Tool<FastMCPSessionAuth, typeof ArtistIdParamSchema> = {
      name: 'get_artist',
      description: 'Get an artist',
      parameters: ArtistIdParamSchema,
      execute: async (args) => {
        try {
          const artistService = new ArtistService();
          const artist = await artistService.get(args);
    
          return JSON.stringify(artist);
        } catch (error) {
          throw formatDiscogsError(error);
        }
      },
    };
  • Input schema (Zod) for the 'get_artist' tool, requiring an artist_id number.
    export const ArtistIdParamSchema = z.object({
      artist_id: z.number(),
    });
  • Registers the 'get_artist' tool on the MCP server within registerDatabaseTools.
    server.addTool(getArtistTool);
  • Top-level tool registration function that invokes registerDatabaseTools, indirectly registering 'get_artist'.
    export function registerTools(server: FastMCP): void {
      registerDatabaseTools(server);
      registerMarketplaceTools(server);
      registerInventoryExportTool(server);
      registerUserIdentityTools(server);
      registerUserCollectionTools(server);
      registerUserWantlistTools(server);
      registerUserListsTools(server);
      registerMediaTools(server);
    }
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Get an artist' implies a read-only operation but doesn't specify authentication needs, rate limits, error handling, or response format. It lacks critical details like whether it returns metadata, images, or other artist data, making it inadequate for a tool with no annotation support.

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

Conciseness5/5

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

The description is extremely concise with just three words, front-loading the core action ('Get an artist'). There's no wasted language or redundancy, making it efficient in terms of brevity, though this conciseness comes at the cost of completeness.

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

Completeness1/5

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

Given the tool's complexity (1 parameter, no annotations, no output schema), the description is incomplete. It doesn't cover what the tool returns, how to use it effectively, or behavioral aspects. For a read operation in a context with many sibling tools, more guidance is needed to make it actionable for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage, and the tool description adds no information about the 'artist_id' parameter. It doesn't explain what an artist_id is, its format (e.g., numeric ID), where to obtain it, or validation rules. With low schema coverage and no compensatory details, this fails to clarify parameter meaning.

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

Purpose2/5

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

The description 'Get an artist' is a tautology that restates the tool name without adding meaningful context. It specifies the verb 'Get' and resource 'artist', but doesn't explain what 'Get' entails (retrieve details, fetch metadata, etc.) or distinguish this from sibling tools like 'get_artist_releases' or 'get_release'. It's minimally functional but lacks specificity.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an artist_id), differentiate from similar tools (e.g., 'get_artist_releases' for releases by an artist), or specify use cases (e.g., for artist profiles vs. discographies). This leaves the agent with no contextual direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cswkim/discogs-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server