Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

yahoo_sports_standings

Fetch grouped league standings from Yahoo Sports pages for a specified league, with optional soccer season filtering, and return structured standings data.

Instructions

Yahoo Sports standings. Returns grouped standings from a Yahoo Sports standings page. Use a league whose standings flag is true in yahoo-sports-leagues. Soccer standings can use a season from yahoo-sports-soccer-scoreboard; competitions without a source table are excluded.

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_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueYesLeague key
seasonNoOptional soccer standings season from yahoo-sports-soccer-scoreboard

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.18
    • changedInput schema / properties / league / enum
      Previous value: -[
      -  "nfl",
      -  "nba",
      -  "wnba",
      -  "mlb",
      -  "nhl",
      -  "college-football",
      -  "college-basketball",
      -  "mls",
      -  "premier-league",
      -  "la-liga",
      -  "serie-a",
      -  "bundesliga",
      -  "ligue-1",
      -  "champions-league",
      -  "nwsl",
      -  "ligamx-apertura",
      -  "ligamx-clausura",
      -  "world-cup"
      -]New value: +[
      +  "nfl",
      +  "nba",
      +  "wnba",
      +  "mlb",
      +  "nhl",
      +  "college-football",
      +  "college-basketball",
      +  "mls",
      +  "premier-league",
      +  "la-liga",
      +  "serie-a",
      +  "bundesliga",
      +  "ligue-1",
      +  "champions-league",
      +  "nwsl",
      +  "ligamx-apertura",
      +  "ligamx-clausura",
      +  "world-cup",
      +  "europa-league"
      +]
    • addedInput schema / properties / season
      Added value: +{
      +  "description": "Optional soccer standings season from yahoo-sports-soccer-scoreboard",
      +  "type": "integer"
      +}
  2. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / league / enum
      Added value: +[
      +  "nfl",
      +  "nba",
      +  "wnba",
      +  "mlb",
      +  "nhl",
      +  "college-football",
      +  "college-basketball",
      +  "mls",
      +  "premier-league",
      +  "la-liga",
      +  "serie-a",
      +  "bundesliga",
      +  "ligue-1",
      +  "champions-league",
      +  "nwsl",
      +  "ligamx-apertura",
      +  "ligamx-clausura",
      +  "world-cup"
      +]
  3. Addedv1.14.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the basic return shape ('grouped standings') and an important exclusion rule, but it does not describe read-only status, data freshness, rate limits, or error behavior.

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 short and front-loaded, starting with what it returns before moving to constraints. There is minor redundancy between the title-like first sentence and the second sentence, but it remains efficient.

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 two-parameter read tool with a rich enum schema, the description gives the essential invocation context: valid league selection, soccer season handling, and exclusions. No output schema exists, but 'grouped standings' is enough to set expectations for this low-complexity tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning beyond the schema. It explains that the league must have a standings flag and that season is relevant for soccer standings sourced from yahoo-sports-soccer-scoreboard.

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 gives a specific verb and resource: it returns grouped standings from a Yahoo Sports standings page. It also clarifies that the league must have a standings flag, which helps an agent distinguish this from generic league lookups, though it does not explicitly contrast with other standings providers.

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

Usage Guidelines4/5

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

It provides clear usage constraints: use a league whose standings flag is true in yahoo-sports-leagues, and for soccer optionally use a season from yahoo-sports-soccer-scoreboard. It also states exclusions for competitions without a source table, though it does not compare against other standings tools.

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