Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_stats

Fetch a complete Yahoo Sports league stats table by league, week, and page type, including live tabs, filters, and sort-stat IDs for querying player or team leaders.

Instructions

Yahoo Sports league stats table. Returns one complete Yahoo stats table (the embedded data can contain up to 200 rows), plus the live tabs, filters and sort-stat catalog. Pagination in Yahoo's table is client-side; no page or offset parameter is added.

Input Schema

NameRequiredDescriptionDefault
weekNoWeek number from stats-discovery; pair with weekSeasonPhase
leagueYesStats league key
pageTypeNoStats page type; defaults to individual
qualifiedNoQualified leaders filter, when listed by stats-discovery
cutTypeIdsNoSplit/situation id from stats-discovery, e.g. HOME
sortStatIdNoSort id from the response's sort_stat_ids, e.g. TOTAL_REBOUNDS_PER_GAME
positionIdsNoPosition id from stats-discovery, e.g. POINT_GUARD
selectedTableNoTab id from the response's tabs list; defaults to 0
leagueStructureNoStructure id from stats-discovery, e.g. nba.struct.conf.1
weekSeasonPhaseNoPhase value paired with week, e.g. REGULAR_SEASON or POSTSEASON

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that the returned table is complete (up to 200 rows embedded), that tabs/filters/sort-stat ids come back in the same response (enabling follow-up calls), and that pagination is client-side so no page/offset exists. It stops short of stating read-only semantics explicitly or any rate-limit/auth constraints, but the behavioral picture an agent needs is largely present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: resource identification, return shape, then the pagination caveat. Front-loaded and free of filler; each sentence conveys information the agent would otherwise have to discover by calling the tool.

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 10-parameter, non-annotated read tool with no output schema, the description covers the two things the agent most needs: what comes back (one table up to 200 rows, plus the tabs/filters/sort-stat catalog) and that pagination is not a caller concern. The remaining gap is the explicit handoff relationship with yahoo_sports_stats_discovery and yahoo_sports_stats_catalog, which is only hinted at.

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?

Schema description coverage is 100% and every one of the 10 parameters already documents its source (e.g. 'Sort id from the response's sort_stat_ids'), so the baseline is 3. The description adds only a negative statement about pagination parameters and no further semantics for week, pageType, qualified, cutTypeIds, etc.

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 names a specific resource ('Yahoo Sports league stats table') and states what is returned: one complete table plus tabs, filters and a sort-stat catalog. It is clear what the tool does, but it never names the closely related siblings (yahoo_sports_stats_catalog, yahoo_sports_stats_discovery), so the agent must infer the division of labor from the schema's prose.

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?

Usage is only implied: the description's mention of a 'sort-stat catalog' and the schema's references to stats-discovery suggest the discovery tool must be called first to obtain ids, and the 'no page or offset parameter' note implicitly says not to attempt pagination. There is no explicit when-to-use versus yahoo_sports_stats_catalog (which presumably returns just the tabs/filters metadata) or stats_discovery, leaving selection to inference.

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