Skip to main content
Glama

List shows

list_shows

Retrieve band shows and filter by upcoming or past dates and booking status to track gigs from enquiry through completion.

Instructions

List shows (gigs). Filter upcoming/past and by booking status (e.g. Enquiry, Confirmed, Advance Received, Completed).

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_shows"
  }
}

Input Schema

NameRequiredDescriptionDefault
whenNoupcoming
limitNo
booking_statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must carry the behavioral disclosure; it only implies a read operation via 'List' and mentions filtering. It omits permissions, pagination/limit behavior, sorting, and return format.

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?

Two short clauses, front-loaded with purpose and then filters; no wasted wording. It remains readable and appropriately sized.

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

Completeness3/5

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

For a simple three-parameter list tool, the definition covers the core purpose and filter options. However, with no annotations or output schema, it lacks behavioral details such as pagination, default limit behavior, and result shape.

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%, and the description explains the when filter and gives examples for booking_status, but it never mentions the limit parameter or the 'all' enum value. It partially compensates for the schema gap but leaves one of three parameters undocumented.

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 definition opens with a specific verb and resource, 'List shows (gigs)', and states the two filtering dimensions. It is clearly a listing tool, though it does not explicitly contrast itself with get_show or other siblings.

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?

It indicates the tool is for filtering upcoming/past shows and by booking status, which gives implied usage. It does not state when to choose it over get_show or list_setlists, nor any when-not conditions.

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