Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_event_stats

Fetch an event's public betting splits (bets and money by spread side) plus each team's last five results and colors; returns 404 when stats aren't published.

Instructions

FanDuel Sportsbook event betting splits and form. Returns one event's public betting split (share of bets and of money on each side of the spread) and each team's last five results, with team colors. Events without published stats return 404.

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent id from any Sportsbook events listing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses useful return content: public betting split shares and each team's last five results. It also states that events without published stats return 404, which is important operational behavior. It does not explicitly confirm read-only safety or rate-limit behavior, but the 'Returns' framing makes the operation type clear.

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 three tight sentences with no filler, and it front-loads the core purpose before detailing returned data and the 404 case. Every sentence contributes useful information.

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?

Because no output schema exists, the description must explain return values, and it does so by naming betting split shares, team form, and team colors. It also covers the key failure case with a 404 for missing stats. The response shape is not fully detailed, but it is sufficiently complete for this simple single-parameter endpoint.

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?

The schema fully documents the single event_id parameter, including that it comes from any Sportsbook events listing. The description adds no further parameter meaning, so the baseline of 3 is appropriate for a 100%-covered single-parameter 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 event's public betting splits and team form. It clearly distinguishes the returned content from a generic box score by naming betting split shares and last-five results. It does not explicitly contrast itself with sibling event-stat tools, but the purpose is still clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives such as fanduel_sportsbook_event_box_score, event_score, or event_play_by_play. The content implies it is for betting splits and recent form, but an agent must infer that from the return description rather than being told when to select it.

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