Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_league

Fetch FanDuel league page events, markets, and odds by tab and U.S. state to power odds comparisons and market feeds.

Instructions

FanDuel Sportsbook league page odds. Returns a featured league page (for example nfl, nba, mlb) with its events, markets and odds, grouped by the page's tabs such as Games, Player Props, Win Totals or Super Bowl. custom_page_id values come from the sports route's popular_links; an unknown id returns 404.

Input Schema

NameRequiredDescriptionDefault
tabNoShow only one tab of this page: a tab slug from the response `tabs[].slug` (the lowercase-hyphenated tab title, such as `games` or `player-props`). An unknown slug returns 400 listing the page's tabs
stateNoU.S. market to query (prices and offered markets differ by state); default nj
market_typeNoKeep only these market types (repeat the parameter or comma-separate), for example `MONEY_LINE`. Valid values are listed in the response `market_types`; unmatched types return no markets
competition_idNoKeep only events of this competition id (from the response `competitions`)
custom_page_idYesLeague page id such as `nfl`, `nba`, `mlb`, `ncaaf`, `ncaab`, `nhl`, `wnba`, `pga`, `ncaaw`. Tournament and event pages appear and disappear during the year, and a retired page returns 404; list the current ones with the sports route
exclude_marketsNoReturn events without their markets (a cheap event listing); `market_types` is still returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that league pages appear and disappear through the year and that retired ids 404, and the schema adds the 400 on an unknown tab. It says nothing about response size, pagination, or whether the whole page is always returned, which matters for a markets-heavy response.

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?

Three sentences, each doing distinct work: what it returns, how the grouping works, and where the id comes from plus its failure mode. The payload description is front-loaded with no filler.

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?

With no output schema, the description adequately sketches the return shape (events, markets, odds, tabs) and covers id discovery and error behavior. Minor gaps remain around response size and whether odds are live-updating versus snapshot, but an agent has enough to call it correctly.

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% with detailed per-parameter text, so baseline is 3. The description still adds value by naming the concrete source of `custom_page_id` (`popular_links` on the sports route) and by explaining that results are grouped by the page's tabs, which motivates the `tab` parameter beyond its schema wording.

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 and payload: a featured league page with events, markets and odds grouped by tabs (Games, Player Props, Win Totals, Super Bowl). That is concrete enough to distinguish it from sibling odds tools, though it never names a sibling (e.g. fanduel_sportsbook_sport or fanduel_sportsbook_competition) explicitly.

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 a clear entry path by saying `custom_page_id` values come from the sports route's `popular_links`, which effectively tells the agent to call the sports route first. It also warns that an unknown id returns 404. It stops short of saying when to pick this over the sport or competition page tools.

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