Browse Fanatics Live shows by league to get live and upcoming listings, including name, status, cover image, viewers, and hosting channel.
Browse Fanatics Live shows by league. Returns the live and upcoming shows currently listed under a Fanatics Live league: name, status, cover image, viewers, and the hosting channel/shop.
| Name | Required | Description | Default |
|---|---|---|---|
| league | Yes | Fanatics Live league type code. See GET /fanaticslive/leagues for the full list. |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It helpfully discloses the returned fields (name, status, cover image, viewers, hosting channel/shop) and that results are scoped to live/upcoming shows, but says nothing about pagination, rate limits, or auth requirements for a network-backed browse call.
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?
Two sentences, zero filler, with the core purpose front-loaded before the return-field detail. Every clause earns its place.
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?
For a one-parameter read tool with no output schema and no annotations, the description covers purpose and the shape of the response adequately. It could be more complete by noting how to discover valid league codes or how it relates to fanaticslive_shop_shows, but nothing essential to invocation is missing.
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?
Schema description coverage is 100% and the league enum is fully documented in the schema, including a pointer to GET /fanaticslive/leagues. The description's 'by league' merely restates the single parameter without adding format or selection detail, so baseline 3 applies.
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?
States a specific verb and resource ('Browse Fanatics Live shows by league') and clarifies scope as live and upcoming shows, which is more precise than the sibling fanaticslive_show. It does not explicitly contrast itself with fanaticslive_shop_shows or fanaticslive_leagues, so it stops short of full sibling differentiation.
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?
Usage is implied by 'by league' and the required league parameter, but there is no explicit when-to-use guidance or reference to alternatives such as fanaticslive_leagues (to obtain the league list) or fanaticslive_shop_shows. The agent must infer the routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.