Skip to main content
Glama

fanduel_sportsbook_league

Read-only

Fetch a FanDuel Sportsbook league page (custom_page_id such as nfl, nba, mlb, ncaaf, ncaab, nhl, wnba, pga, ncaaw) with its events, markets and odds, grouped by tab (Games, Player Props, Win Totals, ...). Unknown ids return not-found; list current ids with fanduel_sportsbook_sports.

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_league"
  }
}

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds useful behavior beyond that: the tab-grouped response shape and the not-found behavior on unknown ids. It omits any note about state/market availability differences on the returned data, which would have made it a 5.

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: the first states what is fetched and its shape, the second covers error behavior and id discovery. Front-loaded with the resource and scope, 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 an output schema present, return values needn't be spelled out, and the description still sketches the tab-grouped structure plus the id-discovery prerequisite. What's missing is guidance on the other optional filters (state, market_type, competition_id) as they apply specifically to league pages, though the schema carries those.

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 schema already documents tab slugs, state codes, market_type values, and event_type_id mappings in detail. The description only restates custom_page_id examples and gestures at tab grouping, adding little beyond what the schema provides. Baseline 3 is appropriate.

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?

Specific verb ('Fetch') and resource ('FanDuel Sportsbook league page'), plus it states what comes back: events, markets, odds grouped by tab. The custom_page_id examples (nfl, nba, pga) pin down the resource identity so an agent can distinguish it from sibling tools like fanduel_sportsbook_event or fanduel_sportsbook_competition.

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?

It names the discovery path explicitly ('list current ids with fanduel_sportsbook_sports') and covers the failure mode ('Unknown ids return not-found'). It doesn't contrast itself against the nearest sibling for a single league's alternatives, but the routing guidance for id acquisition is clear.

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.