Skip to main content
Glama
Sign In

spotify

by com.jojapi
OverviewDiscussionsAdmin

Artist discography overview

get_v1_1_artist_discography_overview

Artist discography overview Group: Artists. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

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_v1_1_artist_discography_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoArtist ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior1/5

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

With no annotations provided, the description must carry the full behavioral disclosure burden. It only mentions billing, not what the tool does (e.g., returns a discography list), side effects, or safety. It fails to disclose any operational behavior.

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

Conciseness2/5

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

The description is short but poorly structured: it mixes a tautological title, a redundant group label, and billing details in a run-on. Most content (billing) is not relevant for tool selection, and the useful purpose is absent.

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?

For a simple tool with one parameter, no output schema, and no annotations, the description provides almost no context: it doesn't state what the tool returns, how it differs from other artist endpoints, or typical usage. An agent cannot confidently select this tool over siblings.

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?

The single parameter 'id' is fully described in the schema with a clear 'Artist ID' description (100% coverage). The description adds nothing about parameters, so the baseline 3 applies.

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 merely repeats the title ('Artist discography overview') with a typo ('disciscography') and adds 'Group: Artists', which is redundant. No verb or specifics distinguish it from sibling tools like get_v1_1_artist_albums or get_v1_1_artist_overview.

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 versus other artist-focused tools. The only extra info is billing (cost and payment method), which is not about usage context or alternatives.

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

All spotify 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