Skip to main content
Glama
fanduelapi-mcp

fanduelapi-mcp

odds_board

Fetch every game's moneyline, spread, and total for a league in one call, grouped by game, with date, market-type, and line-movement filters—instead of reading games one at a time.

Instructions

The odds board: every game of a league with its game lines (moneyline, spread, total) in one call, grouped by game. Use it instead of reading games one at a time: "what are tonight's NBA lines?", "show me every NFL spread this week". Pass date (US Eastern YYYY-MM-DD) for one day, market_type for other families (comma list, or all), and changed_since (an ISO time such as the last call's meta.as_of) to get only markets that moved. With no sport or league it reads the league with the most open game lines. A default call costs 4 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": "odds_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOne US Eastern calendar date, YYYY-MM-DD.
limitNoMarkets, 1 to 1000, default 200.
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.
periodNogame (default), a period such as h1 or q1, or any.
market_typeNoComma list of market families (moneyline, spread, total, team_total, alt_spread, alt_total, ...) or all. Default moneyline,spread,total.
user_requestYesThe current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data.
changed_sinceNoISO time: only markets that moved after it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does substantial work: it discloses the cost model ('a default call costs 4 credits' with a link), the implicit-default behavior when sport/league are omitted, and the incremental-refresh semantics of changed_since. It does not state the response envelope or pagination behavior beyond the limit parameter, so a small gap remains for a read tool of this complexity.

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 purpose before usage and cost, and every sentence carries information (routing examples, defaults, incremental mode, credits). It is dense but not padded; the two quoted example queries could arguably be trimmed, which keeps it just short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter, no-output-schema, no-annotation tool, the definition covers purpose, invocation defaults, parameter formats, incremental semantics, and cost — everything an agent needs before calling. Return shape is the only unstated element, and the meta.as_of reference partially covers even that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning beyond the schema: it clarifies that date is a single US Eastern calendar day, that market_type accepts a comma list or 'all', and — most valuably — that changed_since can be sourced from the last call's meta.as_of, which encodes a workflow the schema alone does not convey.

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?

The description opens with a specific verb-and-resource framing — 'every game of a league with its game lines (moneyline, spread, total) in one call, grouped by game' — and explicitly contrasts itself with the alternative of 'reading games one at a time.' An agent can tell immediately that this is a bulk odds retrieval tool, not a single-game lookup like game_report or line_move.

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?

It gives concrete usage triggers in the user's own language ("what are tonight's NBA lines?", "show me every NFL spread this week"), names the discouraged alternative, and explains the fallback rule when no sport or league is passed ('reads the league with the most open game lines'). It also states when to pass changed_since (incremental refresh after a prior call).

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