Skip to main content
Glama

Last Fm

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.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description adds that the tool is non-destructive and returns results 'ready to call directly, no second schema lookup needed.' No contradictions; the description enriches the behavioral profile beyond annotations.

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?

The description is well-structured: it starts with a clear verb phrase, lists use cases concretely, explains the output format, and ends with usage advice. Every sentence adds value without redundancy.

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?

Despite no output schema, the description explicitly states what is returned (names, descriptions, schemas with examples) and that results are callable directly. Given the tool's discovery purpose and the context of many sibling tools, this description is fully adequate.

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% with descriptions for each parameter, including aliases. The description adds value by providing examples of natural language queries and clarifying that 'query' accepts free-form descriptions. This enhances understanding beyond the schema alone.

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 clearly states the tool finds tools by describing data/task, lists specific domains (SEC filings, financials, etc.), and explains it returns top-N relevant tools with names, descriptions, and schemas. This distinguishes it from sibling tools, which are specific tools rather than a discovery tool.

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?

The description explicitly says 'Call this FIRST when you have many tools available and want to see the option set (not just one answer).' It also specifies when to use (browse, search, look up, discover) and implies when not to (if you already know the tool). This provides strong guidance on usage context.

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

All Last Fm 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
Disambiguation2/5

Many tools have overlapping purposes, especially the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and the Polymarket cluster (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread). Additionally, discover_tools and suggest_questions both serve as discovery/onboarding tools, and ai_visibility_check vs scan_competitor_ai_presence are closely related. While descriptions are detailed, the boundaries between these tools are unclear, causing potential misselection.

Naming Consistency4/5

All tool names use lowercase snake_case with no camelCase or mixed styles. The naming follows a mostly consistent verb_noun or data_subject pattern (e.g., ask_pipeworx, list_subscriptions, validate_claim, artist_info, recent_alerts). Minor deviations exist, such as recent_alerts and user_top_tracks not beginning with a verb, but the overall pattern is predictable and readable.

Tool Count2/5

40 tools is far too many for a server nominally about Last.fm; only 9 tools actually relate to its stated purpose. The remaining 31 tools cover unrelated domains (Pipeworx data routing, Polymarket betting, memory, subscriptions, etc.), making the set bloated and unfocused. Many tools are near-duplicates (ask_pipeworx, _beta, _grounded; four different polymarket_* analysis tools), inflating the count without adding distinct value.

Completeness2/5

Even within the Last.fm domain, the tool surface is incomplete: there is no artist search, album search, user profile info, recent scrobbles, loved tracks, or music recommendations. The unrelated Pipeworx/Polymarket tools, while individually comprehensive for their own domains, do not compensate for the lack of core Last.fm functionality given the server's stated purpose. The overall set is a fragmented mixture that leaves significant gaps for what the server name promises.

Resources