Skip to main content
Glama

fanduel_sportsbook_home

Read-only

Fetch the FanDuel Sportsbook homepage's featured events with markets and current American, decimal and fractional odds, grouped by tab. Filter with tab, competition_id and market_type; exclude_markets returns events only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fanduel_sportsbook_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoShow one tab of the page: a slug from the response tabs[].slug, such as games or player-props.
stateNoU.S. market to query; default nj. One of ar, az, co, ct, dc, ia, il, in, ks, ky, la, ma, md, mi, mo, mr, nc, nj, ny, oh, on, pa, pr, tn, va, vt, wv, wy.
market_typeNoKeep only these market types, such as MONEY_LINE; valid values are listed in the response market_types.
event_type_idNoSport id: 6423 American Football, 1 Soccer, 7522 Basketball, 3 Golf, 7511 Baseball, 7524 Ice Hockey, 2 Tennis, 26420387 Mixed Martial Arts, 2593174 Table Tennis, 3503 Darts, 6 Boxing, 5 Rugby Union, 4 Cricket, 8 Motor Sport, 1477 Rugby League, 6422 Snooker, 468328 Handball, 28608997 Lacrosse; 998917 Volleyball, 4726642 Surfing, 10 Special Bets and 2378961 Politics; availability differs by market and an unoffered sport returns not found. Required for sport and competition.
competition_idNoCompetition id from a response's competitions; required for fanduel_sportsbook_competition, an event filter elsewhere.
custom_page_idNoLeague page id for fanduel_sportsbook_league, such as nfl, nba, mlb, ncaaf, ncaab, nhl, wnba, pga or ncaaw; list current ids with fanduel_sportsbook_sports.
exclude_marketsNoReturn events without their markets for a compact listing.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / event_type_id / description
      Previous value: -"Sport id: 6423 American Football, 1 Soccer, 7522 Basketball, 3 Golf, 7511 Baseball, 7524 Ice Hockey, 2 Tennis, 26420387 Mixed Martial Arts, 2593174 Table Tennis, 3503 Darts, 6 Boxing, 5 Rugby Union, 4 Cricket, 8 Motor Sport, 1477 Rugby League, 6422 Snooker, 468328 Handball, 28608997 Lacrosse; 998917 Volleyball, 4726642 Surfing, 10 Special Bets and 2378961 Politics are Ontario only. Required for sport and competition."New value: +"Sport id: 6423 American Football, 1 Soccer, 7522 Basketball, 3 Golf, 7511 Baseball, 7524 Ice Hockey, 2 Tennis, 26420387 Mixed Martial Arts, 2593174 Table Tennis, 3503 Darts, 6 Boxing, 5 Rugby Union, 4 Cricket, 8 Motor Sport, 1477 Rugby League, 6422 Snooker, 468328 Handball, 28608997 Lacrosse; 998917 Volleyball, 4726642 Surfing, 10 Special Bets and 2378961 Politics; availability differs by market and an unoffered sport returns not found. Required for sport and competition."
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

With readOnlyHint/openWorldHint already covering the safety profile, the description adds real context: the response carries markets plus American, decimal and fractional odds, results are grouped by tab, and exclude_markets yields events without markets. It stops short of describing pagination or size limits, keeping it at a solid 4.

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 tight sentences: the first front-loads what is returned and its shape, the second covers filtering and the exclude_markets toggle. No filler or restated metadata.

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?

An output schema exists, so return values needn't be detailed, and the description still summarizes them. For a zero-required-parameter, read-only homepage feed this is close to complete; the only gap is not flagging the state/market parameter that changes which book results come from.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and each parameter already carries rich documentation (state enum, event_type_id sport ids, tab slugs from tabs[].slug). The description adds no meaning beyond the schema, and notably omits the state parameter entirely. Baseline for full coverage is 3, but the description contributes nothing and misses a meaningful filter, so below baseline.

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 gives a specific verb ('Fetch') and a well-scoped resource ('FanDuel Sportsbook homepage's featured events with markets and ... odds, grouped by tab'). That scope implicitly distinguishes it from event/competition/league siblings, but it never names a sibling tool for contrast, 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?

It lists the filter knobs ('Filter with tab, competition_id and market_type') and explains the exclude_markets shortcut, which implies how to narrow results. However, it never says when to pick this over fanduel_sportsbook_live, _sport, or _competition, so guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.