Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

fanduel_sportsbook_team_schedule

Retrieve a team's FanDuel Sportsbook schedule and results by season block for NFL or NBA, including opponents, venues, scores, opponent records and adjacent games.

Instructions

FanDuel Sportsbook team schedule and results. Returns a team's schedule by season block (preseason, regular season) with opponent, venue, home/away, result and opponent record, plus its previous and next game. Available for the NFL and NBA only.

Input Schema

NameRequiredDescriptionDefault
teamYesTeam slug from the `teams` route (`groups[].teams[].slug`), such as `arizona-cardinals`
leagueYesLeague: `nfl`, `nba`, `mlb`, `college-football`, `college-basketball`

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

B3.4/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 disclosure burden. It usefully lists returned fields (opponent, venue, home/away, result, opponent record, previous/next game), but says nothing about authentication, rate limits, error behavior, pagination, or whether results include future games.

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?

The description is front-loaded with purpose and return fields across three compact sentences. There is minor redundancy between 'team schedule and results' and 'Returns a team's schedule,' but no filler or unnecessary background.

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?

The description adequately explains what is returned, which matters because there is no output schema. However, the league availability statement contradicts the input schema enum, and no alternative schedule tools are referenced, leaving the agent with unresolved ambiguity about valid calls.

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 the baseline is 3. The description introduces season-block grouping but does not explain the team slug, and its NFL/NBA-only statement directly conflicts with the league enum, which allows mlb, college-football, and college-basketball.

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 clearly states the resource and action: 'FanDuel Sportsbook team schedule and results,' and it specifies the returned fields. It does not distinguish this from sibling schedule tools such as fanduel_sportsbook_schedule or yahoo_sports_team_schedule, so it falls short of a 5.

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 'Available for the NFL and NBA only' note gives a usage constraint, but there is no guidance on when to choose this tool over other schedule or team-data siblings. The constraint also conflicts with the schema's five-league enum, making the guidance unreliable.

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