Skip to main content
Glama
chrischall

setlist-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

setlist_unmark_attended

DestructiveIdempotent

Remove a show from your attended setlist.fm list by setlist ID. Reverses mark-attended; no-op if not attended, and verifies removal.

Instructions

Remove a show from YOUR attended list on setlist.fm, by setlist ID (reverses setlist_mark_attended). Authenticated via your session. Idempotent: a no-op if not currently attended. Reversible with setlist_mark_attended. Removes the attendance and verifies by re-reading. 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

TableJSON Schema
NameRequiredDescriptionDefault
setlistIdYesSetlist ID to remove from your attended shows

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 remove 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.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint, but the description adds valuable context: it verifies by re-reading, mentions the attribution requirement for URLs, and clarifies the no-op behavior. This goes beyond annotations without contradicting them, providing a richer understanding of side effects and data handling.

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 dense but every sentence contributes: purpose, authentication, idempotency, reversibility, verification, and attribution requirements. Information is front-loaded with the core action, and the structure is logical. No fluff.

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 simple one-parameter tool with no output schema, the description covers all essential operational aspects: what it does, how it behaves (idempotent), side effects (removes attendance and verifies), authentication, and how to present results. An agent can call it correctly and handle the response appropriately without additional context.

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 coverage is 100% with the parameter described as 'Setlist ID to remove from your attended shows'. The description repeats this but doesn't add new semantic details. Baseline of 3 is appropriate since the schema already documents the parameter well.

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 verb 'Remove' and the resource 'show from YOUR attended list on setlist.fm' with the setlist ID parameter. It explicitly names the reverse operation (setlist_mark_attended), which distinguishes it from siblings. The purpose is unambiguous and specific.

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?

It indicates when to use the tool by stating it 'reverses setlist_mark_attended' and that it is 'Reversible with setlist_mark_attended', implying usage to undo attendance. It also notes authentication via session. However, it doesn't explicitly state when not to use it or list alternatives beyond the reversal, though the context makes it 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