Retrieve Fanatics Live's public shop directory with IDs, names, slugs, logos, and follower counts. Use each slug with /fanaticslive/shop/{slug} to access individual shops.
Get Fanatics Live's shop directory. Returns Fanatics Live's full public shop directory: every shop's id, name, slug, logo, and follower count. Each entry's slug is usable directly with /fanaticslive/shop/{slug}.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 discloses that this is a public directory (implying no auth) and that it returns the 'full' set with named fields, which answers the main behavioral questions for a zero-argument read. It omits rate limits, pagination/refresh behavior, and response format.
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, front-loaded with the purpose, then the return shape and a chaining hint. No filler or redundancy.
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?
With no output schema, no annotations, and no parameters, the description is responsible for conveying both what it does and what comes back; it does list the fields and the completeness of the result. Minor gaps remain around response format and any pagination, 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?
The tool has zero input parameters, so the baseline is 4. The description correctly indicates no filtering or input is involved and instead describes the output shape, which is the only semantic content available.
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 ('Get Fanatics Live's shop directory') and enumerates the returned fields (id, name, slug, logo, follower count), so the agent knows exactly what this yields. It does not name sibling tools like fanaticslive_shop or fanaticslive_shop_shows, but the chaining hint partially distinguishes it.
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 note that each slug works with /fanaticslive/shop/{slug} implies the workflow (discover slugs here, then drill into a shop), which is useful implied guidance. However, there is no explicit when-to-use vs alternatives and no when-not statement against the many fanaticslive_* siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.