Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_competition

Retrieve a FanDuel Sportsbook competition's schedule and futures with markets and odds by passing sport and competition IDs.

Instructions

FanDuel Sportsbook competition schedule and futures. Returns one competition's schedule and futures (tabs schedule and futures) with markets and odds. Get competition_id from the competitions of a league or sport response.

Input Schema

NameRequiredDescriptionDefault
tabNoShow only one tab of this page: a tab slug from the response `tabs[].slug` (the lowercase-hyphenated tab title, such as `games` or `player-props`). An unknown slug returns 400 listing the page's tabs
stateNoU.S. market to query (prices and offered markets differ by state); default nj
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
event_type_idYesSport 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 (Volleyball is also offered in NJ, PA, CO and AZ), and a sport a market does not offer returns 404
competition_idYesCompetition id from a league, sport or home response `competitions`
exclude_marketsNoReturn events without their markets (a cheap event listing); `market_types` is still returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations and no output schema, the description does carry the burden, but it only says the tool returns schedule and futures with markets and odds. It does not describe permission needs, rate limits, pagination, or read-only behavior beyond the implicit 'Returns' wording.

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?

The description is short, front-loaded, and easy to scan across three sentences. There is little waste, though the first sentence partly restates the tool name and the remaining sentences are compact rather than richly informative.

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?

For a six-parameter read tool with no output schema, the description sufficiently explains what is returned and where `competition_id` comes from. It does not elaborate on state-dependent availability, market filtering, or tab errors, but the schema covers those details in depth.

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 all six parameters, including `tab`, `state`, `market_type`, and `exclude_markets`. The description adds only the source of `competition_id` and the two named tabs, both of which are already largely covered in the schema.

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?

The description states a specific resource and scope: one FanDuel Sportsbook competition's schedule and futures, including markets and odds. It is clear what the tool returns, but it does not explicitly distinguish itself from nearby siblings such as `fanduel_sportsbook_schedule` or `fanduel_sportsbook_league`.

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?

The description gives a useful prerequisite: get `competition_id` from a league or sport response's `competitions`. However, it does not state when to use this tool versus `fanduel_sportsbook_schedule`, `fanduel_sportsbook_league`, or event-level tools, leaving alternatives 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