Skip to main content
Glama

Deezer

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Chart

chart
Read-onlyIdempotent

Current chart (top tracks/albums/artists). Pass genre_id 0 for worldwide.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
genre_idNoDefault 0 (all genres).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
albumsNo
tracksNo
artistsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "genre_id": 0
+  },
+  {
+    "genre_id": 132
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "albums": {
+      "properties": {
+        "data": {
+          "description": "Top chart albums",
+          "items": {
+            "properties": {
+              "cover": {
+                "description": "Album cover URL",
+                "type": "string"
+              },
+              "id": {
+                "description": "Album ID",
+                "type": "number"
+              },
+              "title": {
+                "description": "Album title",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "artists": {
+      "properties": {
+        "data": {
+          "description": "Top chart artists",
+          "items": {
+            "properties": {
+              "id": {
+                "description": "Artist ID",
+                "type": "number"
+              },
+              "name": {
+                "description": "Artist name",
+                "type": "string"
+              },
+              "picture": {
+                "description": "Artist image URL",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "tracks": {
+      "properties": {
+        "data": {
+          "description": "Top chart tracks",
+          "items": {
+            "properties": {
+              "duration": {
+                "description": "Duration in seconds",
+                "type": "number"
+              },
+              "id": {
+                "description": "Track ID",
+                "type": "number"
+              },
+              "preview": {
+                "description": "Preview URL",
+                "type": "string"
+              },
+              "title": {
+                "description": "Track title",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and not destructive. The description adds 'Current chart' implying recent data, but doesn't go beyond annotations. No contradictions.

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?

Two sentences, no superfluous words, front-loaded with key purpose. Highly efficient.

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?

Given the tool's simplicity, annotations cover safety, and output schema exists, the description adequately covers purpose and parameter usage. Missing details about genre_id range or return format, but output schema presumably handles that.

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 has 100% coverage with description 'Default 0 (all genres).' The description adds context that 0 means worldwide, which is helpful but only marginally extends the schema's information.

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?

Clearly states it returns the current chart of top tracks/albums/artists, distinguishing from siblings like album, artist, track which focus on individual entities. However, it doesn't specify whether all three categories are returned in one chart or separately.

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?

Provides a usage hint ('Pass genre_id 0 for worldwide') but does not explicitly state when to use this tool versus alternatives like artist or track tools. No guidance on when not to use it.

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

All Deezer toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources