Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

spotify_artist

Retrieve Spotify artist details by providing an artist ID or URL, returning profile data from the Fetchproof API for artist lookups.

Instructions

spotify: Artist. GET /v1/spotify/artist. Provide one of: id, url. Get Spotify artist Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": "spotify_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSpotify artist ID. Provide id or url.
urlNoSpotify artist URL. Provide id or url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a real behavioral trait: a 1-credit charge on success, free on errors/timeouts/invalid requests/cache hits. It says nothing about authentication requirements, rate limiting, what happens if both id and url are supplied, or what a "not found" response looks like beyond the cost note.

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 endpoint and parameter rule are front-loaded and clear, but the final two sentences are long, generic billing boilerplate (blocked, timed-out, invalid, cache hits, published costs) that consumes roughly half the text for a single fact. It is organized but not tight.

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 two-parameter read tool with full schema coverage, the essentials are present, but there is no output schema, so the description should state what an artist result contains. It also omits permission/credential prerequisites and the behavior when both id and url are given, leaving real gaps for an agent invoking it blind.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds a constraint the schema does not encode: required is empty, yet the description states at least one of id or url must be provided ("one of"), clarifying an ambiguity the JSON schema leaves open. That is genuine added meaning, though neither parameter's format is elaborated beyond the schema's own descriptions and example.

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?

"Get Spotify artist" states a verb and a specific resource, and the platform+entity pairing implicitly separates it from spotify_album, spotify_track and apple_music_artist. It never says what artist data is returned (profile, top tracks, albums), and the leading "spotify: Artist. GET /v1/spotify/artist" restates the same fact twice without adding resolution.

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?

The only directive is "Provide one of: id, url", which is an input constraint rather than a when-to-use rule. There is no guidance on when an agent should pick this over apple_music_artist or spotify_track, nor on whether an ID is preferable to a URL when both are available.

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