Skip to main content
Glama
fanduelapi-mcp

fanduelapi-mcp

compare_books

Compare FanDuel player props and game lines with Novig fair prices, DraftKings odds, and PrizePicks lines to calculate EV and spot better sportsbook prices.

Instructions

One FanDuel market next to the same market elsewhere: the Novig fair (no-vig) price, the DraftKings price and the PrizePicks line, with FanDuel's EV against the fair price and the better sportsbook price per side. Use it for "how does FanDuel's line on compare?" or "is FanDuel's total off market?". Covers player props and game lines. Free plan: five minutes behind. A default call costs 3 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": "compare_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1 to 200, default 50.
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.
playerNoPlayer name or part of it.
event_idNoOne FanDuel game's event_id.
market_typeNoOne market type. Default: all.
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/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the data sources behind each column, that FanDuel EV is measured against the no-vig fair price, that free-plan data lags five minutes, and that a default call costs 3 credits. It says nothing about auth or rate limits, and doesn't clarify whether the comparison is a single market or a paged set.

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?

Front-loaded with what is returned, then use cases, then plan and credit constraints – a logical order with no filler. Every sentence adds information an agent would act on.

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, so the description must convey the return shape, and it does so by enumerating the compared prices, EV and per-side best price. Pagination is only hinted at through the schema; nothing is said about ordering or response size, but the definition is otherwise complete for a read-only comparison 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 description coverage is 100%, so league codes, pagination, market_type enum and the required user_request are all already documented in the schema. The description adds only an oblique nod to defaults via 'a default call costs 3 credits'. Baseline 3 applies since the schema does the param work.

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?

The description names a specific verb and resource – placing one FanDuel market side by side with Novig fair price, DraftKings price, PrizePicks line, plus EV and best price per side. It is far from tautological. It never names a sibling (e.g. odds_board or positive_ev) to draw the boundary, which caps it below 5.

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?

Two concrete example phrasings ('how does FanDuel's line on <player> compare?' and 'is FanDuel's total off market?') plus the scope 'covers player props and game lines' give a clear picture of when this fits. There is no explicit when-not guidance or named alternative for a plain board lookup, so it falls short of 5.

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