Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

fanduel_sportsbook_parlays

Retrieve FanDuel Sportsbook parlay cards—popular, same-game and SGP+—with ticket counts, combined odds and legs, filtered by view, sport, competition, market or odds range.

Instructions

FanDuel Sportsbook Parlay Hub. Returns the Sportsbook's Parlay Hub: popular parlays, same-game parlays (SGP) and SGP+ combinations, each with the number of tickets placed on it (total_bets), combined odds, the legs and an editor's narrative when there is one. view picks the list: popular (the homepage list), all (every card, filterable by type), next-to-start (grouped by the events starting soonest) or event (popular cards for one event). The Sportsbook returns at most 50 cards per request. filters lists the competition groups its own filter bar offers. A request returns at most 50 cards (card_cap); truncated is true when it filled that cap, and narrower type, sport, competition or decimal-odds filters reveal the cards beyond it.

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

Input Schema

NameRequiredDescriptionDefault
typeNoCard type filter for `view=all` (repeat or comma-separate): `PARLAY` (multi-event parlay), `SGP` (same-game parlay), `SGP_PLUS` (SGP combined across games)
viewNoWhich list: `popular` (default), `all`, `next-to-start` or `event`
stateNoMarket to query; default nj
event_idNoEvent id, required for `view=event` and rejected otherwise
max_oddsNoMaximum combined decimal odds (1.01 to 10000) for `view=all` and `view=next-to-start`
min_oddsNoMinimum combined decimal odds (1.01 to 10000) for `view=all` and `view=next-to-start`
event_type_idNoSport filter for `view=all` and `view=next-to-start`: 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 (Volleyball is also offered in NJ, PA, CO and AZ), and a sport a market does not offer returns 404
competition_idNoCompetition filter for `view=all` and `view=next-to-start` (repeat or comma-separate, up to 20 ids); the groups in the response `filters` list valid ids

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 burden and does well: it discloses the 50-card cap, that `truncated` marks a full cap, and that narrower type/sport/competition/decimal-odds filters reveal cards past it — real truncation semantics an agent needs. It also notes a sport unavailable in a market returns 404. It does not state auth or rate-limit behavior, which is a minor gap for a public feed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: the return contents come first, then the view/filter semantics, then the truncation caveat. The 50-card cap is stated twice ('at most 50 cards per request' and 'at most 50 cards (card_cap)'), which is redundant but minor.

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 does the work of describing returns: card fields, the `filters` block, and the `card_cap`/`truncated` pagination signals. It never sketches the top-level response shape (e.g., whether cards are a flat list or grouped by event under next-to-start), leaving one gap for an agent planning to parse results.

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%, which sets a baseline of 3, but the description adds meaning beyond the enum labels — it defines what each view returns and how the odds/sport/competition filters interact with `view=all` and `next-to-start`. It also explains that the response `filters` list supplies valid competition_id values, which the schema only gestures at.

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: it returns the FanDuel Sportsbook Parlay Hub cards (parlays, SGP, SGP+). The resource is narrow enough to separate it from sibling feeds like fanduel_sportsbook_home, and it names the per-card fields (total_bets, combined odds, legs, narrative).

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 explicitly explains what each `view` selects — popular as the homepage list, all as every card filterable by type, next-to-start grouped by soonest events, event for one event — and states that event_id is required for view=event and rejected otherwise. It gives no guidance on when to prefer this over adjacent tools such as fanduel_sportsbook_home or fanduel_sportsbook_builder, so sibling routing is left implicit.

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