Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_search

Search FanDuel Sportsbook events and competitions by team, player, or league name to retrieve matching event IDs, competition IDs, and start times by market.

Instructions

FanDuel Sportsbook search. Searches the Sportsbook's events and competitions by text (team, player-event or league names such as lakers or nfl). Events come back in the search index's relevance order with the sport, competition and start time; competitions come back with a match count. Use the returned event_id and competition_id with the event and competition routes.

Input Schema

NameRequiredDescriptionDefault
qYesSearch text, 2 to 100 characters
typeNoWhat to search: `all` (events and competitions), `event` or `competition`; default all
limitNoMaximum events returned, 1 to 50; default 20
stateNoU.S. market to query (prices and offered markets differ by state); default nj
event_type_idNoLimit results to one sport: 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose result ordering (relevance), returned fields (sport, competition, start time; match count for competitions), which is useful. However it says nothing about auth requirements, rate limits, or error behavior such as the market/sport 404 case documented only in the schema.

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?

Three sentences, front-loaded with what it searches, then what comes back, then what to do with the IDs. No filler or restated title.

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 five params, full schema descriptions, and no output schema, the description covers the return shape and next-step usage well. It omits mention of how `limit` interacts with competitions and the 404-on-unavailable-sport behavior, but the schema covers those details.

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 the baseline would be 3. The description adds value by clarifying the searchable domain ('team, player-event or league names such as `lakers` or `nfl`'), which concretely informs how to populate `q` in a way the schema's 'Search text, 2 to 100 characters' does not.

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: 'Searches the Sportsbook's events and competitions by text', with concrete example queries (lakers, nfl) and the shape of results. The purpose is unambiguous. It does not explicitly distinguish itself from close siblings like fanduel_sportsbook_autocomplete or fanduel_sportsbook_search_tabs, which keeps it from a 5.

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 clear forward guidance: 'Use the returned `event_id` and `competition_id` with the event and competition routes', which explains where this tool fits in a workflow. It does not say when to prefer this over autocomplete or search_tabs, so no explicit exclusions or alternatives 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