Skip to main content
Glama
Sign In
setlist-mcp

setlist-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

setlist_mark_attended

Idempotent

Mark attendance on setlist.fm by setlist ID. Records the "I was there" flag on your account, idempotent and verifiable.

Instructions

Record on YOUR setlist.fm account that you attended a show — the site's "I was there" marker — by setlist ID. Authenticated via your setlist.fm session — SETLIST_SESSION_COOKIE, or a signed-in browser tab via the fetchproxy bridge. Idempotent: a no-op if already marked. Reversible with setlist_unmark_attended. Toggles attendance and verifies by re-reading the setlist page. Returns attended, changed and verified. verified: true means the page shows the requested state. If verified is false, the toggle could not be checked: attended holds the state the re-read saw, or null if the page was unreadable, and changed is false — check the show on setlist.fm before reporting success. Results include a setlist.fm url; when you present this data, cite it as a clickable source link to setlist.fm (their API terms require followable attribution — no nofollow). If a result has no url, link to https://www.setlist.fm instead.

Input Schema

NameRequiredDescriptionDefault
setlistIdYesSetlist ID (e.g. from setlist_search_setlists / resolve_concerts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.3
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to actually record attendance; omit for a dry-run preview.",
-  "type": "boolean"
-}
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv0.7.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (which only declare idempotent, non-destructive, open-world). It discloses the auth mechanism (SETLIST_SESSION_COOKIE or fetchproxy bridge), the idempotent no-op semantics, the verify-by-re-read behavior, the meaning of verified/attended/changed, the unreadable-page failure mode, and an attribution obligation. This is exactly the behavioral context an agent needs.

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 core action, then layers auth, idempotency, verification semantics and attribution. Every sentence earns its place, though the return-value and attribution clauses make it longer than strictly minimal.

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?

With no output schema, the description fully compensates by documenting the returned fields (attended, changed, verified), their semantics, the failure mode, and the citation requirement. Nothing an agent needs to call and correctly report this tool is missing.

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?

Only one parameter (setlistId) at 100% schema coverage, so the schema already documents it fully, and the description's 'by setlist ID' adds no new syntax or format detail. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

States a specific verb+resource (record attendance on your setlist.fm account) and immediately disambiguates from the sibling setlist_unmark_attended by naming it as the reversal path. An agent can distinguish it from other setlist_* tools without opening a schema.

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?

Clearly establishes the context (mark attendance for a show) and names the alternative for the opposite action (setlist_unmark_attended). It also notes idempotent no-op behavior, which informs the call. It stops short of explicit when-not guidance, but the routing is clear.

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