Retrieve guest sit-ins and musician appearances from live show history, optionally filtered by a specific person.
Guest sit-ins / musician appearances, optionally filtered to one person.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| person | 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 does not disclose any side effects, permissions, or whether the operation is read-only. With no annotations available, the description carries the full burden, and it fails to mention these aspects.
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 efficiently conveys the core function and optional filtering. There is no unnecessary verbosity or structural complexity.
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 basic context but omits details such as return format, pagination behavior, or how results are ordered. It is adequate for a simple tool but leaves some gaps for an agent unfamiliar with the domain.
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 explains the 'person' parameter as an optional filter but does not clarify the 'limit' parameter. Schema coverage is partial (1 of 2 parameters mentioned), and the description adds some meaning but is incomplete.
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 guest sit-ins or musician appearances, with an optional filter by person. It is concise and unambiguous, though it does not specify the exact output format.
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?
No guidance is provided on when to use this tool versus alternatives like search_shows or song_history. The description lacks any mention of distinct use cases or relationships to sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.