Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

yahoo_sports_player

Fetch a Yahoo Sports player's bio and current-season stats by league and numeric player ID, including soccer and other supported league keys.

Instructions

Yahoo Sports player detail. Returns one player bio and current-season stats. Use league=soccer for Yahoo's flat soccer player namespace, or a league key from yahoo-sports-leagues; get the numeric player id from a roster record.

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>",
      "player": "<player>"
    },
    "name": "yahoo_sports_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueYesLeague key
playerYesNumeric Yahoo Sports player id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.18
    • 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"
      +]
  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

A4.1/5.0
Behavior4/5

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

With no annotations, the description still discloses the key behavioral facts: it returns a single player bio and current-season stats, and that soccer uses a flat namespace. It does not mention authentication, error behavior, or rate limits, but it clearly describes a read-style detail lookup.

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?

The description is three tight sentences with the core purpose front-loaded, followed by the return scope and parameter-sourcing details. There is no redundant or wasted text.

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 simple two-parameter detail lookup with no output schema, the description covers purpose, return content, and how to obtain both required values. It is nearly complete, missing only minor operational details such as invalid-id handling.

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 is 3, but the description adds useful meaning beyond the schema by explaining where to source the league value and the numeric player id. The soccer namespace caveat is genuinely non-obvious parameter guidance.

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 resource and return scope: one player bio plus current-season stats. It is clearly a detail lookup rather than a search or roster endpoint, though it does not explicitly name the search sibling as an alternative.

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 gives practical guidance for both parameters: use a league key from yahoo-sports-leagues or league=soccer for the flat soccer namespace, and obtain the numeric player id from a roster record. It lacks an explicit when-not-to-use clause or direct referral to yahoo_sports_player_search.

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