Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_builder

Fetch FanDuel Sportsbook bet-builder groups, cards, players, and selectable choices for a given event, then price choices separately with builder/quotes.

Instructions

FanDuel Sportsbook bet builder. Returns the Sportsbook's bet-builder content for one event: the groups and cards (bet templates such as who will win, player lines, bullseye ranges, player podium, either-player and head-to-head groups) with their selectable options, the players and teams on offer, the periods and every priceable choice with its choice_id and description. Choices carry no odds here; price them with builder/quotes using this response's ramp_event_id. head-to-head and player-combos return 404 when the event has no cards for that experience.

Input Schema

NameRequiredDescriptionDefault
stateNoMarket code, including `on` for Ontario; default `nj`
event_idYesEvent id from the `builder/events` route (`events[].event_id`)
experienceNoBuilder experience: `yourway` (default), `head-to-head`, `player-combos`, `bullseye`, `player-podium`, `or-bets`

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does it well: it discloses the returned structure (groups, cards, players, teams, periods, choices with choice_id), that choices are unpriced, and that head-to-head and player-combos 404 when no cards exist. Missing auth/market-availability caveats, but the error and return-shape behavior is unusually explicit.

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?

Front-loads the purpose in the first sentence, then layers payload, pricing hand-off, and edge cases. Dense but every sentence carries information; the parenthetical list of card types is slightly heavy but earns its place given no output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A no-output-schema read tool whose behavior, return contents, cross-tool dependency, and failure mode are all stated. An agent has everything needed to call it, interpret the response, and know what to do next.

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%, so baseline is 3; the description earns a bump by explaining what the `experience` values mean behaviorally (which ones 404 when unsupported) and by surfacing `ramp_event_id`, the field needed to chain into builder/quotes. It stops short of explaining the `state` parameter, but that is already covered in 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 Sportsbook's bet-builder content for one event') and enumerates the payload contents, making it clearly distinct from sibling builder_events (listing) and builder_quotes (pricing). An agent can pick this tool 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?

Explicitly routes the follow-up step: 'Choices carry no odds here; price them with builder/quotes using this response's ramp_event_id', and documents exactly when two experiences return 404. Lacks only an upfront statement of prerequisites (event_id comes from builder/events, which is only implied via the schema).

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