Skip to main content
Glama

Get a setlist

get_setlist

Fetch a setlist by ID with its songs in performance order, grouped by section when sections exist.

Instructions

Get one setlist by id with its songs in performance order, grouped by section when sections are used.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "setlist_id": "<setlist_id>"
    },
    "name": "get_setlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
setlist_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does usefully describe output shape (songs ordered by performance, grouped by section when sections exist), which is real behavioral context beyond the schema, but it says nothing about read-only safety, error behavior for an unknown id, or what metadata accompanies the songs.

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?

A single front-loaded sentence with the resource, the key, and the return shape, with no filler. Every clause earns its place.

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 one-parameter read tool with no output schema, the description covers the essential contract: single setlist, lookup by id, songs in performance order and section grouping. The only meaningful gap is how callers are expected to discover a valid setlist_id.

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?

There is one parameter with 0% schema description coverage, so the prose must compensate. "By id" confirms the parameter is an identifier for a single setlist, but it adds nothing about format or expected source of that id, leaving the schema's uuid format to do the remaining work.

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?

The description names a specific verb and resource ("Get one setlist") plus the retrieval key ("by id") and what comes back (songs in performance order, section grouping). The singular "one setlist by id" implicitly separates it from list-style siblings, but it never names them, so the differentiation is inferential rather than explicit.

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?

Usage is only implied: the "by id" phrasing tells an agent this is an id-based detail fetch rather than a search or listing. There is no statement of when to prefer it over list_setlists or how a setlist_id would be obtained, so an agent must infer the workflow.

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