latest_show
The most recent show's setlist.
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?
No annotations exist, and the description does not disclose behavioral traits like whether the tool is read-only, what happens if no shows exist, or if it requires any authentication. The word 'setlist' implies a read operation, but this is not explicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is only five words, which is too brief. While it avoids verbosity, it omits essential details like the optional parameter and any use context, making it under-specified rather than concise.
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 presence of a parameter (include_related) and lack of output schema, the description is incomplete. It does not explain the parameter or the return structure, leaving the agent with insufficient information to use the tool correctly.
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?
The input schema has one parameter (include_related) with no description, and the tool description does not explain what it does. Schema description coverage is 0%, so the description adds no value for parameter understanding.
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 indicates the tool returns the setlist of the most recent show. It implicitly distinguishes from sibling tools like get_setlist (which requires a specific show ID) and search_shows (which searches all shows). However, it lacks an explicit verb like 'retrieve' or 'get', making the action slightly vague.
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 such as get_setlist or search_shows. The description simply states what it does without context about prerequisites, limitations, or when it is appropriate.
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.