Skip to main content
Glama
fanduelapi-mcp

fanduelapi-mcp

list_events

Find upcoming or live FanDuel games by sport or league, then get each event_id, start time, in-play flag, and prop count to choose a game for prop queries.

Instructions

Upcoming and live games FanDuel lists, with each game's event_id, start time, in-play flag and how many props it carries. Use it to find a game before calling list_props with event_id. Filter by sport or league. A default call costs 1 credits (table: https://fanduelapi.com/credits).

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": {
      "user_request": "<user_request>"
    },
    "name": "list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1 to 200, default 50.
sportNoSport, lower case, for example basketball, football, hockey, baseball.
leagueNoLeague code, for example NBA, NFL, NHL, MLB, NCAAB, NCAAF, or a soccer league such as EPL, LALIGA, UCL, MLS.
offsetNoFor the next page when has_more is true.
user_requestYesThe current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description still discloses the credit cost of a call and links to the pricing table, and it spells out what each returned game record contains. It omits auth requirements, rate limits, and behavior when no games match, which keeps it short of 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?

Four short sentences, front-loaded with purpose and return shape, then the routing advice and cost. The opening clause is slightly garbled in word order, but nothing is padding.

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?

There is no output schema, and the description compensates by listing the fields each game record returns, plus cost and filter scope. Pagination is left to the offset/has_more wording in the schema, which is acceptable for this tool's complexity.

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 description coverage is 100%, so limit, sport, league, offset and user_request are already documented. The description only restates that sport and league act as filters, adding little syntax or constraint information beyond the schema.

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?

Names a specific verb and resource ("lists upcoming and live games") and enumerates the returned fields: event_id, start time, in-play flag, and prop count. It is clearly distinguished from list_props, which it positions as the downstream call that consumes event_id.

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

Usage Guidelines5/5

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

"Use it to find a game before calling list_props with event_id" gives an explicit workflow and names the sibling it feeds. The filtering guidance ("Filter by sport or league") further constrains when this tool is the right choice.

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