Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_stats

Retrieve FanDuel Sportsbook betting splits and recent form for upcoming events, including bet/money shares on each spread side and last five results; filter by competition_id.

Instructions

FanDuel Sportsbook betting splits and form for upcoming events. Lists every event the Sportsbook currently publishes stats for: the share of bets and of money wagered on each side of the spread, and each team's last five results. Filter to one competition with competition_id.

Input Schema

NameRequiredDescriptionDefault
competition_idNoKeep only this competition id (for example 12282733 for the NFL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the returned data categories and event scope, but does not state read-only status explicitly, pagination behavior, data freshness, or rate limits.

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?

The description is front-loaded with the core purpose and then efficiently lists the data contents and optional filter. All three sentences provide useful information with no waste.

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 the low complexity, one optional parameter, and no output schema, the description is largely complete: it explains the event scope and the key data returned. It could be slightly stronger by clarifying pagination or freshness, but the essential calling context is present.

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 parameter is already well documented with an NFL example. The description only restates that competition_id filters to one competition, adding no semantics beyond 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: FanDuel Sportsbook betting splits and form for upcoming events, with details on bet/money share and last five results. It is clearer than a generic 'stats' label, but it does not explicitly distinguish itself from closely named siblings such as fanduel_sportsbook_event_stats or fanduel_sportsbook_team_stats.

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 implies when to use it: for upcoming events when you want betting splits and recent form, optionally filtered by competition. However, it gives no explicit when-not guidance or named alternatives, so an agent must infer routing versus other FanDuel stats tools.

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