Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_search_tabs

Search FanDuel Sportsbook matches grouped by sport tabs, filter results by competition pills, and paginate through all available events without markets.

Instructions

FanDuel Sportsbook grouped search. Returns the Sportsbook's own search results, grouped into sport tabs (for example Basketball, Ice Hockey, American Football) and 20 per page. tabs lists the sports that have matches and the selected one is returned in tab; pass a tab title as tab to read another sport. A query without tab also lists competition pills for the selected sport, and passing pill with tab keeps only that competition. found counts the matches in the selected tab (and pill), total_results the matches across the whole query, and next_start_index is the start_index of the next page while more remain. Events and competitions are returned without markets; use the search route for markets.

Input Schema

NameRequiredDescriptionDefault
qYesSearch text, 3 to 100 characters, without `<` or `>`
tabNoSport tab title from a previous response's `tabs[].title`, such as `Basketball`; default is the tab with the most relevant matches
pillNoCompetition title from the response `pills[].title`, such as `NBA`; needs `tab`
stateNoMarket code, including `on` for Ontario; default `nj`
timezoneNoIANA time zone for result times, such as `America/New_York`; default `UTC`
start_indexNoIndex of the first result, 0 to 9999, in steps of 20; default 0

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?

No annotations exist, so the description carries the full burden, and it does substantial work: page size of 20, `next_start_index` as the continuation token, the distinction between `found` (within selected tab/pill) and `total_results` (whole query), and the explicit limitation that events and competitions carry no markets. It stops short of noting auth/geo constraints tied to the `state` parameter, which for a regional sportsbook is a meaningful omission.

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?

Purpose is front-loaded in the first clause, followed by return shape, then parameter behavior, then the scope exclusion. There is no filler or restatement of the name; every sentence adds a distinct fact.

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 6-parameter read tool with no output schema and no annotations, the description is unusually complete: it documents the pagination cursor, the returned tab/pill lists, and both count fields. Remaining gaps are minor — the `state` and `timezone` parameters are left entirely to the schema, and no output structure beyond field names is sketched.

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 would be 3, but the description adds real meaning beyond the schema by explaining the tab/pill interaction (pill requires tab), what the default tab selection means, and how the returned `tabs`, `pills`, and count fields relate to those parameters. This is meaning the schema alone does not convey.

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?

The first sentence names a specific verb and resource ('FanDuel Sportsbook grouped search') and immediately states the output shape — results grouped into sport tabs, 20 per page. It also scopes itself against the sibling 'search' route for markets, so an agent can distinguish the two without opening either 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?

It gives concrete conditional guidance: omit `tab` to get competitions `pills`, pass `pill` with `tab` to narrow to one competition, pass a `tab` title to switch sports. It also explicitly routes market-seekers to 'the `search` route', which is a clear exclusion, though the alternative is named as a route rather than the exact tool `fanduel_sportsbook_search`.

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