Skip to main content
Glama

Setlist Fm

by io.github.pipeworx-io

Artist

artist
Read-onlyIdempotent

Fetch a setlist.fm artist record by band name or MusicBrainz ID. Pass artist_name ("Radiohead") and the name is resolved to the MBID for you, preferring an exact match so a tribute act does not answer for the band; pass mbid directly when you already have one. Returns artist name, MBID, Ticketmaster ID, sort name, and disambiguation info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mbidNoMusicBrainz ID, e.g. "a74b1b7f-71a5-4011-9441-d0b5e4122711". Either this or artist_name is required.
artist_nameNoBand or performer name, e.g. "Radiohead". Either this or mbid is required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNosetlist.fm URL
mbidNoMusic Brainz ID
nameNoArtist name
tmidNoTicketmaster ID
imageNoImage URL
sortNameNoSort name
disambiguationNoDisambiguation info

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context about exact-match preference to avoid tribute acts and explains the name-to-MBID resolution process, going beyond the 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 exceptionally concise: three sentences each serve a distinct purpose (function, parameter usage, return fields). No redundant or filler content.

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?

Given the simple two-parameter tool with 100% schema coverage, output schema, and comprehensive annotations, the description fully covers invocation modes and behavior. It is complete for an agent to select and call this tool.

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 descriptions cover both parameters, but the description enriches them by explaining that artist_name is resolved to an MBID while mbid is used directly, and notes the exact-match preference—details not present in the schema.

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's purpose with a specific verb ('Fetch') and resource ('setlist.fm artist record'), and it distinguishes itself from siblings like artist_search by emphasizing direct lookup with MBID resolution rather than searching.

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

Usage Guidelines4/5

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

Provides clear guidance on when to pass artist_name (to resolve to MBID) versus mbid (when already known), which informs usage. However, it does not explicitly mention alternatives such as artist_search, so exclusions are absent.

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

All Setlist 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

A3.6/5.0
Disambiguation2/5

The tool set mixes two completely different domains: setlist.fm (12 tools) and Pipeworx data services (30+ tools). An agent cannot easily distinguish which tools belong to the server's primary purpose, leading to confusion and misselection.

Naming Consistency2/5

Setlist.fm tools use consistent verb_noun patterns (artist, artist_search, artist_setlists), but the majority of tools follow no unified convention: some use snake_case (ai_visibility_check), others use mixed case (ask_pipeworx), creating an inconsistent naming landscape.

Tool Count2/5

43 tools is excessive for a setlist.fm API. Only about 12 are relevant; the remaining 31 are unrelated and bloat the tool surface, making it hard to navigate and maintain.

Completeness4/5

For the setlist.fm domain, the tools cover search, retrieval, and user data comprehensively (artists, setlists, venues, cities, countries, users). Minor gaps exist (e.g., no update/delete operations), but core workflows are supported.

Resources