Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_research_fixtures

Fetch today's and live FanDuel Research fixtures for NBA, NFL, NHL, and MLB, including status, scores, win probability, TV network, and moneyline, spread, and total odds.

Instructions

FanDuel Research live fixtures. Returns the games on today's slate and in progress for the NBA, NFL, NHL and MLB with status (SCHEDULED, IN_PROGRESS, FINAL), the game clock, each team's score and win probability, the TV network, the Sportsbook event link and the money line, spread and total prices with their market and selection ids. A team's side is home or away when it can be read from the event link. Pass sport to keep one league; a league with no games returns an empty list.

Input Schema

NameRequiredDescriptionDefault
sportNoKeep one league

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the three status values, the returned stat/odds fields, and the honest caveat that `side` is only set 'when it can be read from the event link'. It omits read-only/destructive framing and any rate-limit or freshness caveats, keeping it from a 5.

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?

Front-loaded with the core purpose, then the field list, then the filter rule. It is field-dense and runs long in a single block, but essentially every clause carries information an agent would otherwise have to guess.

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?

No output schema exists, so the description must describe returns, and it does so thoroughly, including the odds/market-id detail and the caveat on `side`. What is missing is any indication of response shape/ordering or pagination, which matters little for a single-slate tool.

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 single enum parameter is fully documented, so the baseline is adequate. The description adds only the behavioral consequence of the filter (empty list for a league with no games) rather than new semantics about the values themselves.

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 and resource ('Returns the games on today's slate and in progress') constrained to four named leagues, and enumerates the payload (status, clock, scores, win probability, network, event link, money line/spread/total with ids). An agent can distinguish this from scoreboard or schedule tools without inspecting the 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?

The 'today's slate and in progress' framing plus 'Pass `sport` to keep one league' gives clear conditions for use, and the empty-list note tells the agent what a miss looks like. It does not name sibling alternatives (e.g. fanduel_sportsbook_schedule or fanduel_sportsbook_live_scores) nor state when to prefer them, so it stops short of full routing guidance.

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