Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

yahoo_sports_team

Fetch a Yahoo Sports team detail record by league and team slug to retrieve team information for standings, scoreboards, or league-specific pages.

Instructions

Yahoo Sports team detail. Returns one team detail record. Use league=soccer for Yahoo's flat soccer team namespace, or a league key from yahoo-sports-leagues for its own team page. Team slugs come from scoreboard or standings records.

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>",
      "team": "<team>"
    },
    "name": "yahoo_sports_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamYesYahoo Sports team slug
leagueYesLeague key

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

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose output cardinality ('one team detail record') and implies a read-only lookup, but is silent on failure behavior for unknown slugs/league keys, and does not describe what the record contains.

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?

Four short sentences, front-loaded with the resource and followed by the disambiguation rule, with no filler. The opening pair ('team detail' / 'returns one team detail record') is mildly redundant but reinforcing rather than wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With two required params, no annotations and no output schema, the description covers input derivation well but says nothing about what fields a team detail record contains or how granular it is. Adequate to invoke correctly, incomplete for judging result usefulness before calling.

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% and the league enum is self-documenting, so the baseline is 3. The description adds real value above baseline by explaining the non-obvious overlap between 'soccer' and the competition-specific keys (flat namespace vs. own team page), and by stating where team slugs must be sourced.

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?

States a specific resource and shape: 'Yahoo Sports team detail. Returns one team detail record,' which tells an agent this is a single-team lookup rather than a list. It does not explicitly distinguish itself from adjacent siblings such as yahoo_sports_team_roster or yahoo_sports_team_schedule, leaving that inference to the agent.

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?

Gives concrete call-construction guidance: use league=soccer for the flat soccer namespace or a league key from yahoo-sports-leagues, and supplies the provenance of team slugs (scoreboard or standings records). That chaining advice is genuinely actionable, but there is no explicit statement of when to prefer a sibling tool (roster, schedule, player) instead.

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