Skip to main content
Glama

List setlists

list_setlists

Retrieve band setlists newest first, with a configurable limit, to review recent shows and performance order.

Instructions

List setlists, newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_setlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses the sort order, which is genuine behavioral context, but says nothing about pagination or truncation — with only a limit parameter and no offset/cursor, an agent cannot tell how to reach results beyond the first page, nor what a setlist record contains.

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?

A single short, front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification given the undocumented limit parameter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations, no output schema and an undocumented parameter, the description leaves out what a setlist includes, whether results are truncated at limit, and how ordering interacts with the limit. An agent can call it, but cannot predict the shape or completeness of the response.

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?

Schema description coverage is 0%, so the description must compensate and does not: the single limit parameter is never mentioned. The schema conveys its type, default of 20 and bounds of 1-100, but the description adds no meaning about what is being limited or what happens when it is hit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List setlists") plus the ordering rule "newest first", which is more than a restatement of the title. It implicitly distinguishes itself from the singular get_setlist sibling via "List", but never says so explicitly.

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

Usage Guidelines3/5

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

The list-vs-get distinction and the "newest first" ordering hint at when to use this rather than get_setlist, but there is no explicit when-to-use statement, no mention of alternatives such as list_shows or list_songs, and no preconditions.

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