Skip to main content
Glama
Sign In
mcp-deezer

mcp-deezer

by Benitoow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_recommendations

Find new music tailored to your taste. Get personalized track suggestions based on your listening habits to help you discover songs you'll love.

Instructions

Personalized recommendations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
playlists_firstNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It does not state whether the tool is read-only, requires authentication, or has any side effects. The name suggests a read operation, but the description fails to confirm or elaborate.

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

Conciseness3/5

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

The description is extremely short (two words), which is concise but at the expense of informativeness. It is front-loaded but lacks the necessary detail to be useful. It earns a middle score because it is not verbose, but it is under-specified.

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

Completeness2/5

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

Given the complexity of the domain (music recommendations, 27 sibling tools), the absence of an output schema, and 0% schema description coverage, the description is severely incomplete. It does not address what the tool returns, how parameters affect results, or how it differs from similar tools.

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

Parameters2/5

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

The input schema has one parameter ('playlists_first') with no description. The tool description does not explain the parameter's meaning or effect. With 0% schema description coverage, the description provides no additional semantic value.

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

Purpose3/5

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

The description 'Personalized recommendations.' states the general purpose (getting recommendations that are personalized) but lacks specificity. Among many sibling tools like get_similar_artists, get_similar_tracks, get_flow, it does not clarify what kind of recommendations (e.g., tracks, artists, playlists). It is a step above a tautology but vague.

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 guidelines are provided. There is no indication of when to use this tool versus alternatives like get_similar_tracks, get_flow, or get_charts. The description offers no context 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