Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

spotify_doctor

Read-onlyIdempotent

Run read-only diagnostics for Spotify MCP auth, token expiry, scopes, Premium gating, rate limits, config, and tool availability, showing why registered tools are trimmed.

Instructions

Run read-only diagnostics: token presence/expiry, auth-time scopes vs write tools enabled by active toolsets, Premium gating, rate-limit cooldown, config state, visible account details when reachable, and the live registered-tool surface with toolset/scope/READONLY trim causes. The only live request is GET /me; no mutation requests are issued.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verboseNoInclude per-check technical detail lines when response_format is concise
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}
  2. Changed5 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / response_format / default
      Added value: +"concise"
    • changedInput schema / properties / response_format / description
      Previous value: -"Response format: concise (default) returns human-readable text, detailed adds metadata, json returns structured data"New value: +"'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object"
    • changedInput schema / properties / verbose / description
      Previous value: -"Include per-check technical detail lines in the prose output"New value: +"Include per-check technical detail lines when response_format is concise"
  3. Changed1 schema field changedv1.28.0
    • addedInput schema / properties / response_format
      Added value: +{
+  "description": "Response format: concise (default) returns human-readable text, detailed adds metadata, json returns structured data",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
  4. Addedv1.26.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value beyond that by naming the specific checks performed and stating the network footprint ('The only live request is GET /me; no mutation requests are issued'), which tells the agent this cannot alter state. It stops short of describing cost, latency, or failure modes of the checks.

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

Conciseness4/5

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

Front-loaded with the verb and mode ('Run read-only diagnostics:') followed by a compact enumeration, then a closing sentence that bounds the network behavior. The enumerated list is long but each item is a distinct diagnostic, so it earns its place.

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?

An output schema exists, so return-value explanation is not required, and the description covers scope, safety, and the one outbound call. The main gap is the absence of guidance on when to run it versus the other diagnostic/toolset 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?

Schema description coverage is 100% and both parameters (verbose, response_format) are fully documented in the schema, including the enum semantics for response_format. The description adds nothing about how verbose or response_format interact, so the baseline 3 applies — the schema carries the full burden.

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?

Specific verb+resource ('Run read-only diagnostics') followed by a concrete enumeration of what is checked: token expiry, scopes, Premium gating, cooldown, config, account, and registered-tool surface. An agent immediately knows this is an environment/health check rather than a data or playback tool. It does not explicitly distinguish itself from nearby diagnostic siblings like toolset_report, inspect_tool, or find_tool, which mention overlapping toolset/scope concerns.

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?

Usage is only implied ('diagnostics' suggests troubleshooting when auth, scopes, Premium, or rate limits are suspect), but there is no explicit when-to-use statement or 'use X instead' routing against toolset_report or inspect_tool. An agent must infer the trigger condition.

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