Skip to main content
Glama
fanduelapi-mcp

fanduelapi-mcp

arbitrage

Find arbitrage and middles across FanDuel, DraftKings, and Novig: two-leg markets at different prices with equal-payout stakes, or line windows where both legs win.

Instructions

Arbitrage across FanDuel, DraftKings and Novig: two sides of one market at different venues whose prices guarantee a profit, with stakes that pay the same either way. type=middles finds middles (two lines with a window where both legs win). Use it for "any arbs on tonight's NBA games?". Developer plan and up; Free gets a short labelled sample and the upgrade link. A default call costs 5 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": "arbitrage"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoDefault arbitrage.
booksNoOnly rows with a leg at this book: fanduel or draftkings.
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.
playerNoPlayer name or part of it.
min_profitNoMinimum guaranteed profit in percent.
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

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does a decent job: it states the covered books, that a default call costs 5 credits with a link to the pricing table, and that Free-plan callers get a short labelled sample plus an upgrade link while Developer plan and up get full results. Missing is any statement of result shape or ordering, but cost and plan-gating are exactly the kind of non-obvious behavior an agent needs.

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?

Dense but nearly every clause earns its place: definition, mode semantics, example query, plan gating, credit cost. The ordering is slightly scattered (mode explanation interrupts the definition), but nothing is padded and the core definition is front-loaded.

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?

For an 8-parameter, no-annotation, no-output-schema tool, the description covers the hard parts an agent would otherwise guess: pricing, plan limits, book coverage, and the middles mode. Only the returned row shape and pagination behavior are left unstated, which is a modest gap rather than a blocking one.

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 the baseline is 3, and the description adds genuine meaning on top: it explains that type=middles means two lines with a window where both legs win, which the schema only labels as 'Default arbitrage.' Book coverage (FanDuel, DraftKings, Novig) also clarifies the books filter, though it never mentions Novig in the books enum context.

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 defines the resource precisely: cross-book arbitrage between FanDuel, DraftKings and Novig, where two legs of one market guarantee equal payout, plus the alternate type=middles mode. An agent can tell what the tool returns conceptually. It does not, however, distinguish itself from conceptually adjacent siblings such as positive_ev or compare_books.

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

Usage Guidelines3/5

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

One concrete trigger phrase is given ('any arbs on tonight's NBA games?') plus the mode switch for middles, which is real usage context. But there is no when-not-to-use guidance and no named alternative, so an agent deciding between this and positive_ev or compare_books gets no routing help.

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