Skip to main content
Glama

Spotify

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\")"New value: +"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\"). Accepts task, q, description, search as aliases."
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "look up FDA drug approvals"
+  },
+  {
+    "query": "analyze housing market trends"
+  }
+]
  3. First observed

TDQS

A4.4/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. The description adds valuable behavioral context beyond that: it returns 'top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed.' This explains the return behavior and the 'no second lookup' convenience. It does not mention rate limits or auth, but with annotations covering safety, this is solid.

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?

Three sentences covering purpose, usage, and return structure. The sentence listing domains is long but informative; it could be trimmed, but it earns its place by showing the breadth of covered topics. Front-loaded with the primary purpose, so it is efficient and well-structured.

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

Completeness5/5

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

For a meta-tool with no output schema, the description is remarkably complete. It explains when to use it, what it returns (top-N tools with schemas and examples), and that results are directly callable. Given the large sibling set, the 'Call this FIRST' guidance is crucial and provided. No obvious gaps.

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%, so the baseline is 3. The description adds context that the 'query' parameter should be a natural language description of the data or task, and mentions 'top-N' which aligns with the 'limit' parameter. However, it does not go beyond what the schema already states about aliases and defaults, so no extra credit beyond baseline.

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

Purpose5/5

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

The description begins with a specific verb+resource: 'Find tools by describing the data or task.' It clearly distinguishes itself from siblings by focusing on tool discovery rather than data access, and even states 'Call this FIRST when you have many tools available.' The domain list (SEC filings, FDA drugs, etc.) further clarifies scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit usage guidance is provided: 'Use when you need to browse, search, look up, or discover what tools exist for...' and 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' This tells the agent when to choose this tool over the many siblings, though it could mention what not to use it for.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation1/5

The tool set is a chaotic mix of Spotify music tools and an extensive Pipeworx data querying system, with no clear separation. Tools like 'ask_pipeworx', 'ask_pipeworx_grounded', and 'deep_research' have overlapping querying purposes, while unrelated tools from prediction markets and company research further muddy the boundaries. An agent would struggle to distinguish which tool to use for a given task.

Naming Consistency2/5

Naming conventions are inconsistent: Spotify tools follow a verb_noun pattern (e.g., 'get_album', 'search'), while Pipeworx tools use descriptive phrases (e.g., 'ask_pipeworx', 'bet_research'). Additionally, some tools have vague names like 'process' or 'run' that could apply to anything. The lack of a unified naming scheme makes the set feel disjointed.

Tool Count2/5

With 36 tools, the count is high, but the server name 'Spotify' implies a focused music service. The majority of tools are unrelated to Spotify (e.g., Pipeworx queries, Polymarket bets, dependency scanning), making the tool count feel inflated and inappropriate for the stated domain. A more focused set would be far more coherent.

Completeness1/5

If this is a Spotify server, it is severely incomplete: it lacks playlist management, user actions, and recommendation features beyond top tracks. The inclusion of dozens of unrelated tools (financial data, prediction markets, package analysis) suggests the server has no clear purpose, leaving it neither complete for Spotify nor for any other single domain.

Resources