Find every show played on a specific calendar date (month and day) across all years, with an option to include related performances.
Every show played on a given calendar day (month 1-12, day 1-31), across years.
| Name | Required | Description | Default |
|---|---|---|---|
| day | Yes | ||
| month | Yes | ||
| include_related | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description conveys a read-only behavior with no side effects, but lacks detail on authentication, rate limits, or the effect of the optional include_related parameter. Without annotations, the agent is left with an incomplete behavioral model.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that directly conveys the core functionality without unnecessary verbosity or redundancy. It is well-structured and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description provides the basic query parameters and their ranges, but it does not describe what the returned data contains (e.g., show details, venue, date). Even though an output schema is indicated, the agent lacks a clear expectation of the response structure, making the call less predictable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description only clarifies that month must be 1-12 and day 1-31, but does not explain the meaning or purpose of include_related. With three parameters and zero schema descriptions, the coverage is minimal, leaving a required parameter undocumented in terms of impact.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: retrieving every show played on a given calendar day across years. The verb 'played' implies a read operation, and the scope (month/day, all years) is unambiguous, distinguishing it from other tools like search_shows or random_show.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for a calendar-day lookup across years, but it does not explicitly state when to prefer this tool over siblings (e.g., search_shows). No conditions or alternatives are mentioned, leaving the agent to infer appropriate use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.