Skip to main content
Glama
Sign In
mcp-deezer

mcp-deezer

by Benitoow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_artist

Retrieve artist details including biography, top tracks, and albums by providing an artist ID, enabling quick access to comprehensive artist information.

Instructions

Get artist details with bio, top tracks, albums.

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": {
      "artist_id": "<artist_id>"
    },
    "name": "get_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
artist_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description bears full burden for behavioral disclosure. It only states 'Get' implying read-only, but fails to mention authentication, rate limits, or any potential side effects. Minimal transparency beyond the basic operation.

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 a single, well-formed sentence with no unnecessary words. It conveys the essential purpose efficiently.

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

Completeness3/5

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

For a simple getter, the description covers the response contents (bio, top tracks, albums) but omits the required parameter. Given no output schema and sibling tools, it is adequate but not fully complete.

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?

Schema description coverage is 0%. The description does not mention the required artist_id parameter, nor does it provide any guidance on its format or usage. The agent must infer entirely from the schema, which lacks textual cues.

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?

Description clearly states the tool retrieves artist details including bio, top tracks, and albums. The verb 'Get' specifies the action, and the resource 'artist details' with examples distinguishes it from sibling tools like get_track or get_similar_artists.

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

Usage Guidelines2/5

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

No guidance on when to use this tool over alternatives. Despite many sibling tools (e.g., get_album, get_similar_artists), the description does not provide context or criteria for selection.

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

Deploy Server

Other Tools