Skip to main content
Glama

fanduel_sportsbook_events_status

Read-only

Get the live state of up to 30 FanDuel Sportsbook events in one call: status, game phase and the clocks that change when prices or status change. Use it to poll many events cheaply; it needs event ids, and unknown ids are listed in not_found rather than failing the call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "fanduel_sportsbook_events_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoU.S. market to query; default nj.
event_idYesEvent ids, 1 to 30.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses the 30-event batch cap, that clocks change when prices/status change, and that unknown ids return in not_found rather than failing — useful partial-result semantics. It doesn't cover rate limits or how stale the 'live' data can be, but the added context is solid.

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?

Two tightly packed sentences, front-loaded with the core purpose and scope, with the usage hint and partial-result caveat following. No wasted words.

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?

An output schema exists so return values needn't be explained, and annotations cover the safety profile; the description fills the important gaps (batch limit, partial results, polling intent). Rate-limit/freshness detail would be the only remaining gap, making it near-complete.

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 both params (event_id array, state with nj default) are documented, so the baseline is 3. The description restates the 'needs event ids' requirement and the 30 cap already in the schema; the not_found note is return-value behavior rather than parameter meaning, so it adds little 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?

Specific verb+resource: 'Get the live state of up to 30 FanDuel Sportsbook events,' and enumerates the returned fields (status, game phase, clocks). It clearly conveys batch status polling but never names or contrasts the many live-related siblings (fanduel_sportsbook_live, live_data, live_scores, live_count), so differentiation is inferred rather than stated.

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?

'Use it to poll many events cheaply' gives a clear usage context (batch live polling), and 'it needs event ids' signals the prerequisite. No explicit when-not or named alternative is offered, so it stops short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.