Skip to main content
Glama
fanduelapi-mcp

fanduelapi-mcp

positive_ev

Identify FanDuel wagers priced above fair odds using Novig no-vig probability, with EV, edge, and Kelly stake details for value betting.

Instructions

+EV bets: FanDuel prices that pay more than the fair chance, measured against the Novig exchange's no-vig price for the same side and line. Use it for "what are the best +EV FanDuel bets right now?" or "is there value on points?". Each row has the FanDuel price, the fair probability and price, ev_pct, edge_cents, Kelly stakes, main_line and confidence. books=fanduel,draftkings adds DraftKings prices. Free plan: top 10, 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": "positive_ev"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoDefault ev.
booksNoComma list: fanduel (default), 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.
event_idNoOne FanDuel game's event_id.
min_edgeNoMinimum EV in percent, -3 to 100.
min_probNoMinimum fair probability in percent. Default 15.
alt_linesNoInclude alternate lines. Default false (main lines only).
confidenceNoDefault high.
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/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses free-plan truncation (top 10), data staleness (five minutes behind), and a concrete cost model (3 credits per default call, with a link to the credit table). It omits auth requirements and pagination/caching behavior, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the definition, then usage examples, then output shape, then cost/plan constraints — a logical funnel with no filler. Even the credit URL earns its place by quantifying the cost claim.

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 a 12-parameter tool with no output schema and no annotations, the description supplies the missing pieces: what each returned row contains (price, fair probability/price, ev_pct, edge_cents, Kelly stakes, main_line, confidence), freshness, and plan limits. An agent can call this correctly and set expectations for the response without further information.

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, but the description adds genuine meaning beyond the schema: books=fanduel,draftkings is explained as augmenting results with DraftKings prices, and the mention of main_line and confidence in each row clarifies what alt_lines and confidence actually control. It doesn't explain min_edge versus min_prob trade-offs, so it's not a full 5.

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 resource (+EV bets) and defines the exact computation: FanDuel prices paying more than the fair chance, benchmarked against Novig's no-vig price for the same side and line. This is precise enough to distinguish it from siblings like arbitrage, compare_books, and odds_board without opening any schema.

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?

Gives concrete trigger phrasings ("what are the best +EV FanDuel bets right now?" and "is there value on <player> points?"), which maps cleanly to a user intent. It stops short of stating when to prefer arbitrage or compare_books instead, so the routing to siblings is left implicit.

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