Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

yahoo_sports_team_roster

Retrieve a Yahoo Sports team roster by specifying league and team slug to get the player list for that team.

Instructions

Yahoo Sports team roster. Returns one team roster. Use league=soccer for Yahoo's flat soccer team namespace, or a league key from yahoo-sports-leagues. Team slugs come from team or scoreboard 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_roster"
  }
}

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.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the non-obvious soccer namespace behavior and that exactly one team's roster is returned, but omits that this is a read-only, non-mutating operation, and says nothing about payload size, failure modes, or whether an unknown slug errors versus returns empty.

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?

Three short sentences, front-loaded with what the tool returns, followed by input-sourcing guidance. No filler; the only mild redundancy is restating the tool name in sentence one.

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?

A simple two-parameter lookup with both parameters documented in the schema and no output schema to explain. The description closes the main practical gap (where to obtain valid league/team values). Roster contents are left implicit, which is a minor omission for a tool whose output is self-describing.

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 already 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema: where each parameter value originates and why 'soccer' behaves differently from the enumerated domestic soccer leagues. That resolves ambiguity in a 28-value enum the schema alone does not explain.

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 verb and resource ('Returns one team roster' for Yahoo Sports), which is more precise than the name alone. It does not, however, explicitly distinguish itself from nearby siblings such as yahoo_sports_team, yahoo_sports_team_schedule, or espn_team_roster, so an agent must infer the boundary.

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 sourcing guidance: league keys come from yahoo-sports-leagues, team slugs come from team or scoreboard records, and soccer uses a flat namespace. That is clear context for qualifying inputs, though no explicit 'do not use this when…' exclusion against alternative roster/team tools is offered.

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