Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

yahoo_sports_team_schedule

Fetch a Yahoo Sports team schedule by league and team slug, returning game details for that team.

Instructions

Yahoo Sports team schedule. Returns one team schedule. 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_schedule"
  }
}

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.6/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 full behavioral burden; it does imply a read-only single-record retrieval, but says nothing about coverage (season range), pagination, or freshness of schedule data. It adds some behavior ('returns one team schedule') but not enough for a zero-annotation tool.

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 action and scope, then the two parameter caveats. No filler, though the sentences are clipped to the point of being slightly telegraphic.

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, non-mutating lookup with full schema description coverage, the description supplies the two things an agent would otherwise get wrong (soccer league handling and team slug provenance). A note on what date range or season the schedule spans would close the remaining gap.

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 baseline is 3, but the description adds real value beyond the schema: league=soccer selects Yahoo's flat soccer namespace rather than a per-competition key, and team slugs must come from team or scoreboard records. Those are non-obvious sourcing rules the schema cannot express.

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+resource pair ('Yahoo Sports team schedule', 'Returns one team schedule') and the singular scope is unambiguous. It does not name the closest sibling (yahoo_sports_league_schedule) to draw the contrast explicitly, so an agent must infer the difference from the word 'team'.

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?

The description routes the agent to prerequisite tools — league keys come from yahoo-sports-leagues, team slugs from team or scoreboard records — which is useful procedural guidance. However it never says when to prefer this over yahoo_sports_league_schedule or the schedule catalog, so true when/when-not guidance is absent.

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