Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticslive_show

Fetch a Fanatics Live show's detail page by ID to view status, viewers, hosting channel/shop, active break/lot, and full break/lot list from public GraphQL data.

Instructions

Get a Fanatics Live show's detail page. Returns a Fanatics Live live show's detail page: status, viewers, hosting channel/shop, its currently active break/lot, and its full break/lot list. Public data sourced from Fanatics Live's own GraphQL API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFanatics Live show id, e.g. from a browse result's id field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral transparency burden. It usefully discloses that the data is public and sourced from Fanatics Live's GraphQL API, and notes the active break/lot is current. It does not mention output formatting, error behavior, or rate limits.

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 text is short and front-loaded, but the opening is redundant: 'Get a Fanatics Live show's detail page' is followed by 'Returns a Fanatics Live live show's detail page.' The phrasing could be tightened and the 'live show's' typo removed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, read-only detail lookup, the description provides the essential context: the resource, the public data source, and the key return fields. It does not fully specify response shape, but with no output schema the listed fields give an agent enough to invoke and understand the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter is fully documented in the schema, including an example source ('from a browse result's id field'). The description adds no parameter-level detail beyond identifying the resource, so the high-coverage baseline of 3 applies.

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 states a specific action and resource: 'Get a Fanatics Live show's detail page,' and enumerates the returned content (status, viewers, hosting channel/shop, active break/lot, and full break/lot list). This makes the tool's role clear, though it does not explicitly differentiate it from sibling tools like fanaticslive_channel or fanaticslive_shop.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage is implied: an agent should call this when it needs a single show's detail page, especially after obtaining an id from a browse result. However, the description does not state when to prefer this tool over related Fanatics Live tools or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools