Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_schedule

Retrieve FanDuel Sportsbook schedules for NFL, NBA, MLB, and college football games, including teams, start times, status, venues, broadcasts, and scores by week or date range.

Instructions

FanDuel Sportsbook league schedule. Returns a league's games with teams, start time, status, venue, broadcast network and scores. The NFL is selected by week (default: the current week; the response lists every week id in weeks) or by date and end_date; college football by date and end_date (default: today, UTC); the NBA and MLB by date (default: today, UTC). Available for the NFL, NBA, MLB and college football.

Input Schema

NameRequiredDescriptionDefault
dateNoFirst day as `YYYY-MM-DD`. Required form for the NBA and MLB (default today, UTC); optional for the NFL and college football
weekNoNFL only: week id from the response `weeks` list, such as `7`; default is the current week. Cannot be combined with `date`
leagueYesLeague: `nfl`, `nba`, `mlb`, `college-football`
end_dateNoNFL and college football only: last day as `YYYY-MM-DD`, at most 31 days after `date`; default is `date` alone

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the returned fields (teams, start time, status, venue, broadcast network, scores), the default windows per league, the 31-day cap on end_date, and that `week` and `date` are mutually exclusive. It omits authentication, rate limits, and result-size/pagination behavior.

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 tight sentences, front-loaded with purpose and return fields before the per-league mechanics. Some redundancy with the schema's parameter descriptions, but nothing wasted.

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?

No output schema and no annotations, but the description covers return contents, defaults, league coverage, and the mutual exclusion of `week` and `date`, which is enough to call it correctly. Error cases and response size are the only notable gaps.

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 coverage is 100%, so the baseline is 3; the description largely restates what the schema already says (date formats, league-specific requirements, the week/date exclusion). The one genuine addition is that the response lists every valid week id in `weeks`, which explains where `week` values come from.

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 ('FanDuel Sportsbook league schedule') and the verb implicitly ('Returns a league's games'), plus enumerates the returned fields. The word 'league' distinguishes it from the sibling fanduel_sportsbook_team_schedule, though the sibling is never named.

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 per-league selection guidance: NFL by `week` or `date`/`end_date`, college football by `date`/`end_date`, NBA and MLB by `date`, with defaults (current week, today UTC) spelled out. It never states when to prefer a sibling such as fanduel_sportsbook_team_schedule or fanduel_sportsbook_event 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