Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_builder_events

Lists bet-builder events grouped by competition with start times and team logos, helping users select an event_id to query the builder route.

Instructions

FanDuel Sportsbook bet builder events. Lists the events a bet-builder experience covers (currently NFL and NBA games), grouped by competition, with start times and team logos. Use an event_id from here with the builder route.

Input Schema

NameRequiredDescriptionDefault
stateNoMarket code, including `on` for Ontario; default `nj`
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/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose useful scope: currently NFL/NBA games, grouped by competition, with start times and logos. It does not mention pagination, authentication needs, rate limits, or whether state/experience filtering changes coverage, which are notable gaps for a tool with no structured safety metadata.

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?

Two sentences with zero waste; the tool purpose and current sport coverage are front-loaded, followed by the key downstream usage note. Every sentence earns its place.

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?

Given low complexity, rich schema coverage, and no output schema, the description is largely complete: it explains what the list contains, current sport coverage, and how to use the resulting `event_id`. It could say more about state/experience defaults or filtering behavior, but those are covered in the schema.

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%, and both `state` and `experience` are already documented with descriptions and an enum. The description adds only the phrase 'bet-builder experience' and the downstream `event_id` usage, not additional parameter semantics, so baseline 3 is appropriate.

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 ('Lists') and resource ('bet builder events'), plus scope details such as current NFL/NBA coverage, competition grouping, start times, and team logos. It also distinguishes itself from the related `builder` route by directing the agent to use an `event_id` from this listing.

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 says to use an `event_id` from these results with the `builder` route, which gives clear downstream context. However, it does not state when to prefer this tool over related siblings like `fanduel_sportsbook_builder` or `fanduel_sportsbook_builder_quotes`, nor does it describe exclusions.

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