Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_league_schedule

Retrieve Yahoo Sports league schedule game records by league, date, week, season, phase, or conference filter. Use catalog values to choose valid seasons, weeks, and filters before querying.

Instructions

Yahoo Sports league schedule games. Returns full game records for the selected date or week from Yahoo's league schedule page. Use yahoo-sports-schedule-catalog for the current seasons, week/phase pairs and NCAA conference/division filter values. The page's own leagueFilter query is applied by Yahoo before the response is parsed.

Input Schema

NameRequiredDescriptionDefault
dateNoOptional date filter in YYYY-MM-DD form; for schedule pages with date tabs
weekNoOptional week value from yahoo-sports-schedule-catalog
leagueYesYahoo league key
seasonNoOptional season year from yahoo-sports-schedule-catalog
seasonPhaseNoOptional week phase from the catalog
leagueFilterNoExact leagueFilter value from the schedule catalog (NCAAF/NCAAB/NCAAW conference, division or Top 25 option)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that full game records are returned and that leagueFilter is applied by Yahoo before parsing, but it omits auth requirements, rate limits, pagination behavior, and read-only framing.

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 uses three front-loaded sentences with no fluff. It efficiently communicates purpose, return scope, catalog dependency, and leagueFilter handling.

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 six-parameter schedule lookup with full schema coverage and no output schema, the description covers purpose, returned records, catalog dependency, and leagueFilter processing. It leaves date/week interaction and pagination behavior unaddressed, so it is not fully complete.

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 description coverage is 100%, so all six parameters are already documented in the schema. The description's mention of date/week selection and catalog-sourced season/week/phase/filter values largely echoes the schema and adds little syntax or constraint detail beyond it.

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 it returns league schedule game records for a selected date or week and identifies Yahoo's league schedule page as the source. It distinguishes its role from yahoo-sports-schedule-catalog by assigning catalog lookup duties, though it does not explicitly contrast with yahoo_sports_team_schedule.

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 explicitly tells the agent to use yahoo-sports-schedule-catalog for current seasons, week/phase pairs, and NCAA conference/division filter values, giving useful prerequisite context. It does not explicitly state when to choose this tool over team-level schedule tools, so some selection inference remains.

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