get_artistFetch a Discogs artist profile by artist_id. Returns name, real name, profile bio, URLs, aliases, group memberships, images, and Discogs URL.
| Name | Required | Description | Default |
|---|---|---|---|
| artist_id | Yes | Discogs artist ID |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "artist_id": 125959
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "description": "Artist profile information from Discogs API",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, etc. Description adds specific return fields and parameter context, enhancing transparency beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with no waste. Front-loaded action verb and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple get-by-ID tool with output schema, description covers input and output adequately. No missing context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with description of artist_id matching schema's 'Discogs artist ID'. Adds minimal extra meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states 'Fetch a Discogs artist profile by artist_id' with specific verb and resource, and lists return fields. Distinguishes from sibling tools like get_label and get_release.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies use when needing an artist profile by ID, but lacks explicit when-to-use guidance or alternatives (e.g., when to prefer search or entity_profile).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.