Skip to main content
Glama

fanduel_sportsbook_parlays

Read-only

List the FanDuel Sportsbook Parlay Hub: popular parlays, same-game parlays and SGP+ combinations with the number of tickets placed (total_bets), combined odds and legs. Use view all with type, event_type_id, competition_id and odds filters, next-to-start for the soonest games, or event for one event_id; returns at most 50 cards.

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 types for view all: PARLAY, SGP (same-game parlay) or SGP_PLUS.
viewNoWhich list: popular (default), all, next-to-start or event.
stateNoMarket to query; default nj.
event_idNoEvent id, required for view event.
max_oddsNoMaximum combined decimal odds for views all and next-to-start.
min_oddsNoMinimum combined decimal odds for views all and next-to-start.
event_type_idNoSport id for views all and next-to-start, such as 7522 for basketball.
competition_idNoCompetition ids for views all and next-to-start; the response filters list valid groups.

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. 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=true and openWorldHint=true, so safety is covered; the description adds the useful behavioral constraint that it 'returns at most 50 cards.' It doesn't discuss state/market defaults, pagination beyond the cap, or freshness, so it adds context but not richly.

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, zero waste, with the resource and content types front-loaded and the view-mode routing following. Every clause carries actionable information.

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, a rich 8-parameter schema, and readOnly/openWorld annotations, the description covers the essentials and even the result cap. Only minor gaps remain (state/market default behavior, what happens with combined filters), so it is nearly complete.

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% and each parameter already documents which views it applies to and its allowed values, so the schema does the heavy lifting. The description reinforces the view-to-filter relationships but introduces no syntax, units, or edge-case detail beyond what the schema provides — baseline 3.

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 ('List the FanDuel Sportsbook Parlay Hub') and enumerates the exact content types (popular parlays, same-game parlays, SGP+ combinations) with the fields returned (total_bets, combined odds, legs). An agent can distinguish this from the many fanduel_sportsbook_* siblings without opening the schema.

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 explicit routing among the tool's own modes: 'view all' with type/event_type_id/competition_id/odds filters, 'next-to-start' for the soonest games, or 'event' for one event_id. No exclusion or comparison against sibling tools (e.g. fanduel_sportsbook_event or fanduel_sportsbook_home), so it stops short of a 5.

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.