Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

fanduel_sportsbook_home

Fetch FanDuel Sportsbook homepage featured events with their markets and current American, decimal, and fractional odds, grouped by tabs and filterable by tab, competition, or market type.

Instructions

FanDuel Sportsbook homepage odds. Returns the Sportsbook homepage's featured events with their markets and current American, decimal and fractional odds, grouped by the homepage's tabs. Filter with tab, competition_id and market_type.

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`)
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.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 does disclose the payload shape (featured events, markets, three odds formats, tab grouping), but omits state-dependent pricing nuances and the fact that unknown tab slugs return 400 — details that live only in schema parameter text. Read-only nature is implied but never stated.

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?

Two sentences with no filler, and the purpose statement is front-loaded ahead of the filtering note. Every clause carries information about what is returned or how to narrow it.

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 explains the return shape (events, markets, odds formats, tab grouping), and the schema fully covers inputs. The main gap is that `state` — which materially changes prices and offered markets — is not surfaced in the description despite being the one parameter with real decision weight.

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 schema already documents all five parameters thoroughly, establishing baseline 3. The description names only three filters (`tab`, `competition_id`, `market_type`) and says nothing about `state` or `exclude_markets`, adding no semantic value beyond the schema.

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?

States a specific verb and resource: returns the FanDuel Sportsbook homepage's featured events with markets and odds, grouped by tabs. The 'homepage' scope cleanly separates it from event-, sport-, league- and search-oriented siblings in the fanduel_sportsbook_* family without needing to name them.

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?

Says 'Filter with `tab`, `competition_id` and `market_type`', which implies the homepage-browse use case and how to narrow it. But there is no explicit when-to-use, no when-not, and no pointer to alternatives such as the event, sport, or trending tools when homepage content is not what the agent wants.

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