Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_event

Fetch FanDuel Sportsbook event markets and odds for a chosen tab, state, and market type, and list available tabs so you can compare lines and player props.

Instructions

FanDuel Sportsbook event markets. Returns one event with the markets and odds of one tab (game lines, player props, quarters, same-game-parlay markets and more). tabs lists every tab the event offers, each with the slug accepted by tab; the default is popular, which holds the most markets. An unknown tab returns 400 listing the valid slugs; an ended event returns 404.

Input Schema

NameRequiredDescriptionDefault
tabNoTab slug from the response `tabs[].slug` (for example `popular`, `passing-props`, `1st-half`, `td-scorer-props`); default `popular`. Tabs differ by sport
stateNoU.S. market to query (prices and offered markets differ by state); default nj
event_idYesEvent id from any Sportsbook events listing
market_typeNoKeep only these market types (repeat the parameter or comma-separate), for example `MONEY_LINE`. Valid values are listed in the response `market_types`; unmatched types return no markets

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden and does meaningfully: it discloses that only one tab's markets are returned, that the response includes a `tabs` array with valid slugs, and the failure semantics (400 with valid slugs for an unknown tab, 404 for an ended event). It does not cover rate limits, auth, or state-dependence of pricing beyond the schema's note.

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?

Four compact sentences, front-loaded with what is returned and immediately followed by the tab/scope rule and the two error cases. Nothing is padded or repeated.

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?

For a 4-param read tool with full schema descriptions and no output schema, the description supplies the missing pieces: single-tab scoping, slug provenance, default behavior, and error semantics. An agent could call this correctly without further context.

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, but the description adds value by explaining where a `tab` slug comes from (the response `tabs[].slug`), that tabs differ by sport, and that `popular` holds the most markets. The `market_type` filtering behavior is already fully documented in the schema, so this is additive rather than redundant.

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?

States a specific verb and resource: returns one FanDuel Sportsbook event with the markets and odds of a single tab. It also enumerates what 'markets' means (game lines, player props, quarters, SGP), so scope is concrete. It does not distinguish itself by name from siblings like fanduel_sportsbook_market_prices or draftkings_event_markets.

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?

Usage is implied rather than stated: the agent learns it needs an event_id and that the default tab is `popular`, but there is no explicit 'use this instead of X when...' and no prerequisites such as how to obtain an event_id beyond the schema's mention of an events listing. No exclusions are given.

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