Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

yahoo_sports_stats

Read-only

Fetch a current Yahoo Sports stats table for a supported league and page type using selectedTable, filters, sortStatId, week, or season values from yahoo_sports_stats_discovery.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "league": "<league>"
    },
    "name": "yahoo_sports_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekNoOptional. Yahoo week number. Supply with weekSeasonPhase when that page exposes week options.
leagueYesRequired. Stats category. Use yahoo-sports-stats-catalog to discover the exact supported set.
page_typeNoOptional. One of individual, weekly, or team when supported by the league. Defaults to individual.
qualifiedNoOptional. Yahoo filter: true for qualified leaders or false for all players, when available.
cut_type_idsNoOptional. Yahoo split/situation value from the stats discovery filter_config.
position_idsNoOptional. Yahoo player-position value from the stats discovery filter_config.
sort_stat_idNoOptional. Yahoo sort-stat id from the stats response sort_stat_ids.
selected_tableNoOptional. Tab index from the stats response tabs, e.g. 0 or 1. Defaults to 0.
league_structureNoOptional. Yahoo league structure value from the stats discovery filter_config.
week_season_phaseNoOptional. Yahoo week phase paired with week, e.g. REGULAR_SEASON or POSTSEASON.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the table is 'current' and that values come from discovery, but it does not add details about rate limits, data freshness, or failure behavior beyond what annotations provide.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no filler. It is somewhat dense because it lists several parameter names inline, but overall it is appropriately sized for 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?

With 10 parameters, full schema descriptions, and an output schema, the description does not need to explain return values or every parameter. It provides the essential context that this fetches a stats table using discovery-derived values, though the mention of 'season' values without a corresponding schema parameter is a minor mismatch.

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%, so the schema already documents all parameters thoroughly. The description mentions selectedTable, filters, sortStatId, week, and season, but this largely repeats parameter concepts already covered in the schema without adding much semantic detail.

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 verb and resource: fetch a current Yahoo Sports stats table for a supported league and page type. It does not explicitly distinguish this tool from yahoo_sports_stats_discovery or yahoo_sports_stats_catalog, so it is clear but lacks sibling differentiation.

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?

It implies that parameter values should come from yahoo_sports_stats_discovery, which is useful prerequisite context. However, it does not explicitly say to call discovery first, nor does it explain when to use this tool rather than the discovery/catalog siblings.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources