upcoming_shows
Announced upcoming shows (dates on or after today).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| include_related | No |
good_wook
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It does not disclose whether the tool is read-only, how results are ordered, pagination behavior, or what 'announced' means regarding cancellation status. The parameter 'include_related' is left unexplained.
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 short (one sentence), which is efficient but at the cost of missing crucial details. It earns a middle score for conciseness but lacks structure.
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 tool has only one optional parameter and no output schema, the description should at least explain the parameter and mention ordering or scope. It fails to provide a complete picture, leaving the agent with insufficient context.
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 description coverage is 0%, and the description does not explain the 'include_related' parameter. The agent cannot infer what 'related' entails, leading to potential confusion.
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 clearly states that this tool returns announced upcoming shows with dates on or after today, distinguishing it from siblings like 'latest_show' or 'search_shows'. However, it lacks an explicit verb (e.g., 'list').
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or when not to use it.
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
B3.2/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: setlist retrieval, jam chart, show search, song stats, venue info, etc. No overlap or ambiguity among the 11 tools.
Naming Consistency5/5
All tool names use consistent snake_case with descriptive verb_noun patterns (e.g., 'get_setlist', 'search_shows', 'song_history'). The outlier 'ping' is a standard health check name.
Tool Count5/5
With 11 tools, the server is well-scoped for its purpose—covering setlist, song, venue, and show operations without clutter or sparsity.
Completeness4/5
The tool surface covers core Phish show information comprehensively: setlists, song stats, jam charts, venue data, and show search. Minor gaps (e.g., absence of review or attendance tools) are acceptable.