upcoming_shows
Announced upcoming shows (dates on or after today).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| include_related | No |
good_honker
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits like pagination, data source, or response format. Only a basic statement of what is returned, lacking depth.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very brief (one sentence), which is concise but omits necessary information about parameters. It is front-loaded with the purpose, but the lack of param details reduces effectiveness.
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?
Given the simplicity (1 param, no output schema), the description fails to explain the parameter or provide context like ordering or filtering. The tool is incomplete for an agent to use confidently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% as the description does not mention the single parameter 'include_related'. The schema only provides type and default, leaving the agent without any explanation of the parameter's purpose.
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?
Description clearly states the tool lists upcoming shows with a specific time filter (on or after today). The verb 'listing' is implied, and the resource is shows. This distinguishes it from siblings like search_shows or latest_show.
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?
No explicit guidance on when to use vs alternatives. However, the name and description imply it's for future shows, and siblings cover other cases. Without explicit comparisons, it's adequate but not proactive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.5/5.0
Disambiguation5/5
Each tool targets a distinct aspect of the band's data: albums, appearances, setlists, jams, shows, songs, venues, etc. There is no overlap in functionality, making it easy for an agent to select the correct tool.
Naming Consistency5/5
All tool names follow the snake_case convention (e.g., album_info, get_setlist, song_stats). The naming is descriptive and consistently uses nouns or verb_noun patterns without mixing styles.
Tool Count5/5
With 14 tools, the server is well-scoped for a band discography/event database. Each tool serves a clear purpose and the count is balanced—neither too few nor excessive.
Completeness5/5
The tool set covers all key operations: searching shows, retrieving setlists, accessing song history and stats, managing albums, venues, jams, appearances, and even health checks. There are no obvious gaps in covering the band's data lifecycle.