Skip to main content
Glama

Last Fm

by io.github.pipeworx-io

Chart Top Artists

chart_top_artists
Read-onlyIdempotent

The world's most-popular music right now — global top artists by listener count. PREFER for "recommend popular music", "top songs / top artists this year", "what music is trending", "popular songs 2026" and any general most-popular-music question (for a GENRE use tag_top_artists; for one NAMED user's history use the user_* tools). Keyless, returns ranked artist names with listener and play counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
artistsNoGlobal top artists container

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, non-destructive. The description adds behavioral context: returns ranked artist names with listener and play counts, and notes keyless access. No contradictions.

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?

Two sentences front-load the core purpose and immediately provide usage guidance and exclusions. No filler.

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?

For a single-parameter read-only tool with output schema, the description covers purpose, usage, and output format. Minor gap is limit parameter semantics, but that is already handled in parameter dimension.

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

Parameters2/5

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

The schema has only 'limit' with no description (0% coverage). The description does not mention the limit parameter, its default, or allowed values, leaving the agent to infer its semantics solely from the property name and example.

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 provides global top artists by listener count, using 'world's most-popular music right now' and explicitly contrasts with tag_top_artists for genre and user_* tools for named user histories. This distinguishes it from siblings.

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 PREFER list with example queries and exclusions for genre and user-specific cases. Also notes keyless operation, which helps the agent know there are no auth prerequisites.

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