Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_team_odds

Fetch a FanDuel Sportsbook team odds page by league and team slug to get championship futures, upcoming game money lines, spreads, totals, and NFL/NBA player props with odds.

Instructions

FanDuel Sportsbook team odds page. Returns a team's odds page: futures prices for its league's championship (Super Bowl, NBA Finals, World Series, national championship), its upcoming games with money line, spread and total for both sides, and player props with selection ids and odds. Available for every league; props appear 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

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral load and does a good job: it explains what data categories are returned, that player props include selection ids and odds, and that props only appear for NFL and NBA. It does not mention currency, freshness, or pagination, but for a read-only odds page lookup the disclosure is strong.

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 is front-loaded with the core identity, followed by a compact enumeration of returned data and one key coverage caveat. Every sentence adds value, with no repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, read-only lookup with no output schema, the description is complete: it explains the main content returned and the important league-conditioned limitation on player props. An agent has enough information to decide whether calling it will produce the needed odds data.

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 the baseline is 3, but the description adds meaningful parameter-dependent behavior: the league choice affects whether player props are present. The team parameter itself is left to the schema, which already gives the required slug format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it returns a team's FanDuel sportsbook odds page, then enumerates the exact content: futures, game lines, and player props. It is clearly distinguishable from sibling tools like fanduel_sportsbook_team_schedule or fanduel_sportsbook_team_stats.

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?

It gives a useful coverage constraint (available for every league; props only for NFL and NBA), but it never says when to use this tool instead of related siblings such as fanduel_sportsbook_market_prices or fanduel_sportsbook_player_props. The usage context is implied rather than explicitly routed.

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