search_shows
Find shows by year, city, state, and/or venue name.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | ||
| year | No | ||
| limit | No | ||
| state | No | ||
| venue | No | ||
| include_related | No |
good_honker
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must fully disclose behavior. It only lists filters but omits details like ordering, pagination, rate limits, or whether it's a read operation. The agent has little insight into side effects or constraints.
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 concise (one sentence) and front-loaded with the verb and resource. However, it is overly brief and could benefit from additional structure or detail without sacrificing conciseness.
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 6 parameters, no output schema, and no annotations, the description is insufficient. It doesn't explain return format, pagination behavior, or the effect of 'include_related', leaving significant gaps for the agent.
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%, so the description must compensate. It mentions year, city, state, and venue but omits 'limit' and 'include_related'. It adds some meaning but not enough to fully understand parameter roles.
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 uses a clear verb ('Find') and resource ('shows') and specifies the filtering criteria. However, it doesn't distinguish this tool from siblings like 'upcoming_shows' or 'random_show', which could cause confusion.
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 are no explicit mentions of context or exclusions, leaving the agent to infer usage from the description alone.
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.