Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

yahoo_sports_game

Fetch a Yahoo Sports game boxscore by league and game slug, or a soccer game_url, to get matchup, line score, team stat totals, play-by-play, and win-probability data.

Instructions

Yahoo Sports game boxscore. Returns one source game boxscore with matchup, line score and team stat totals, plus Yahoo's play-by-play and win-probability timeline when available. Event objects retain Yahoo's sport-specific fields. Use league plus game for direct league pages, or league=soccer with the exact game_url from a soccer scoreboard for competitions whose game path is published per match.

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

Input Schema

NameRequiredDescriptionDefault
gameNoYahoo game slug for direct league pages; supply game or game_url
leagueYesLeague key
game_urlNoExact game.url from a soccer scoreboard; requires league=soccer and cannot be combined with game

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.17.18
    • changedInput schema / properties / game / description
      Previous value: -"Yahoo Sports game slug from a scoreboard/team-schedule response's game url"New value: +"Yahoo game slug for direct league pages; supply game or game_url"
    • addedInput schema / properties / game_url
      Added value: +{
      +  "description": "Exact game.url from a soccer scoreboard; requires league=soccer and cannot be combined with game",
      +  "type": "string"
      +}
    • changedInput schema / properties / league / enum
      Previous value: -[
      -  "nfl",
      -  "nba",
      -  "wnba",
      -  "mlb",
      -  "nhl",
      -  "college-football",
      -  "college-basketball",
      -  "college-womens-basketball",
      -  "mls",
      -  "premier-league",
      -  "la-liga",
      -  "serie-a",
      -  "bundesliga",
      -  "ligue-1",
      -  "champions-league",
      -  "nwsl",
      -  "ligamx-apertura",
      -  "ligamx-clausura",
      -  "copa-america",
      -  "club-world-cup",
      -  "world-cup",
      -  "concacaf-champions-cup",
      -  "concacaf-gold-cup",
      -  "concacaf-league"
      -]New value: +[
      +  "nfl",
      +  "nba",
      +  "wnba",
      +  "mlb",
      +  "nhl",
      +  "college-football",
      +  "college-basketball",
      +  "college-womens-basketball",
      +  "soccer",
      +  "mls",
      +  "premier-league",
      +  "la-liga",
      +  "serie-a",
      +  "bundesliga",
      +  "ligue-1",
      +  "champions-league",
      +  "nwsl",
      +  "ligamx-apertura",
      +  "ligamx-clausura",
      +  "copa-america",
      +  "club-world-cup",
      +  "world-cup",
      +  "concacaf-champions-cup",
      +  "concacaf-gold-cup",
      +  "concacaf-league",
      +  "womens-world-cup",
      +  "europa-league",
      +  "euro-championship"
      +]
    • changedInput schema / required
      Previous value: -[
      -  "league",
      -  "game"
      -]New value: +[
      +  "league"
      +]
  2. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / league / enum
      Added value: +[
      +  "nfl",
      +  "nba",
      +  "wnba",
      +  "mlb",
      +  "nhl",
      +  "college-football",
      +  "college-basketball",
      +  "college-womens-basketball",
      +  "mls",
      +  "premier-league",
      +  "la-liga",
      +  "serie-a",
      +  "bundesliga",
      +  "ligue-1",
      +  "champions-league",
      +  "nwsl",
      +  "ligamx-apertura",
      +  "ligamx-clausura",
      +  "copa-america",
      +  "club-world-cup",
      +  "world-cup",
      +  "concacaf-champions-cup",
      +  "concacaf-gold-cup",
      +  "concacaf-league"
      +]
  3. Addedv1.14.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden of disclosure and does a good job explaining the returned payload, including conditional availability of play-by-play and win-probability data. It also notes that event objects retain sport-specific fields, though it does not discuss error behavior or prerequisites beyond the parameters.

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 front-loaded and appropriately sized for a data-retrieval tool. There is minor redundancy between 'Yahoo Sports game boxscore' and 'Returns one source game boxscore,' but it does not impede understanding.

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 three-parameter retrieval tool without an output schema or annotations, the description is complete enough: it explains what is returned, what is conditional, and how to specify soccer games via game_url. It omits guidance on obtaining non-soccer game slugs and error cases, but the schema covers the parameter mechanics.

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 coverage is 100%, so the schema already documents game, league, and game_url thoroughly. The description reinforces the game_url requirement and adds the condition that it applies to competitions whose game path is published per match, but it largely repeats what the schema provides.

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 clearly states a specific resource and action: it returns a Yahoo Sports game boxscore with matchup, line score, team stats, play-by-play, and win-probability data. It distinguishes itself from a scoreboard implicitly by saying it returns one game boxscore, but it does not name or explicitly contrast with siblings such as yahoo_sports_scoreboard.

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 gives practical invocation guidance for choosing between league+game and league=soccer+game_url, including the requirement to use an exact game_url from a soccer scoreboard. However, it does not explicitly state when to use this tool versus scoreboard or schedule siblings, nor does it describe 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