Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_events_status

Fetches live status, game phase, and change clocks for up to 30 FanDuel Sportsbook events in one call, listing unknown event IDs in not_found.

Instructions

FanDuel Sportsbook events status. Returns the live state of up to 30 events in one call: status (for example ACTIVE), game_phase (for example PRE_PLAY) and the three logical clocks that change when prices, status or structure change, which makes it a cheap way to poll many events. Ids the Sportsbook does not know are listed in not_found instead of failing the call.

Input Schema

NameRequiredDescriptionDefault
stateNoMarket code, including `on` for Ontario; default `nj`
event_idYesEvent ids, 1 to 30, repeated or comma-separated

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the batch cap of 30, the returned fields, and notably that unknown ids land in `not_found` instead of failing the call — an error-handling trait an agent cannot get from the schema. It omits whether the call requires auth or rate limits, but the read-only nature is clear from 'Returns'.

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?

Roughly three sentences, each earning its place: what is returned, why it matters (cheap polling), and how bad ids are handled. The core return contract is front-loaded before the rationale.

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?

With no output schema, the description steps in to describe return fields and error behavior, which is the right coverage for a 2-parameter read tool. The 'three logical clocks' are alluded to without naming them, leaving a small gap for an agent interpreting the response.

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 already documents both `event_id` (1 to 30, repeated or comma-separated) and `state` (market code, default nj). The description restates the 30-id cap and adds the not_found behavior for unknown ids, but adds no new meaning for the `state` parameter, so baseline 3 applies.

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?

States a specific verb and resource: 'Returns the live state of up to 30 events in one call', and enumerates the fields returned (status, game_phase, clocks). It never names a sibling (e.g. fanduel_sportsbook_event or fanduel_sportsbook_live_data) to sharpen the boundary, so it stops short of full differentiation.

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?

'Makes it a cheap way to poll many events' gives a clear usage context: batch polling over many ids. It stops short of explicit when-not guidance or naming the alternative tool for single-event detail, which an agent must infer.

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