Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_live_data

Fetch live in-play sports data from FanDuel Sportsbook for up to 20 events, including scores, game progress, and player prop updates across tennis, soccer, basketball, hockey, and more.

Instructions

FanDuel Sportsbook live state for any sport. Returns live state for up to 20 events from the Sportsbook's in-play service, which covers every sport: tennis sets, games, points and server; soccer score, cards and corners; basketball and hockey period scores and remaining time, with live progress of player-prop markets where the sport has them. details keeps the provider's sport-specific structure; home_score and away_score are filled when the sport reports a single score. Scheduled events return live: false; ids with no entry are listed in missing.

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent id from any Sportsbook events listing; repeat the parameter or comma-separate, 1 to 20 ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.5/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 does well: it discloses sport-specific coverage, the details/home_score/away_score return structure, that scheduled events return live:false, and that missing ids appear in missing. It does not state read-only semantics, auth needs, or rate limits, but those are minor for a live-data read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, and subsequent sentences are dense but each adds output or edge-case information. It is slightly long but justified because no output schema exists.

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 single-parameter tool with no annotations or output schema, the description supplies enough return-shape and edge-case information to call it correctly. It leaves only minor gaps around auth/error behavior beyond the missing ids case.

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 coverage is 100% and the event_id schema description already explains that ids come from listings and can be repeated or comma-separated up to 20. The description adds little parameter-specific meaning beyond echoing the up-to-20-event scope, so the baseline 3 is appropriate.

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 (FanDuel Sportsbook live state) and scope (up to 20 events, any sport) with concrete output detail. It does not explicitly contrast with sibling live/live_scores tools, so it is clear but not fully differentiated.

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 when-to-use or when-not guidance and no alternative tools are named. The description only provides behavioral facts about scheduled and missing events, leaving the agent to infer that this is the tool for live event state.

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