Skip to main content
Glama
fanduelapi-mcp

fanduelapi-mcp

game_report

Generates a full betting report for one game: period lines, player props with line moves and alternate ladders, plus biggest movers. Use it for weekly reports or game research notes.

Instructions

Everything for one game in one call: game lines for every period, every player prop with its move since open and FanDuel's alternate ladder for it, a count by stat and the biggest movers. Use it for a weekly betting report or a research note on one game ("full odds and player props for Chiefs vs Bills"). Find the event_id with list_events or odds_board. A default call costs 8 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": {
      "event_id": "<event_id>",
      "user_request": "<user_request>"
    },
    "name": "game_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesThe game's event_id from list_events or odds_board.
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?

No annotations are supplied, so the description carries the full disclosure burden and does much of it: it details what gets returned and discloses cost (8 credits for a default call) with a link to the credit table. Remaining gaps are pagination, latency, and error behavior for a bad event_id.

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 payoff, then use case, then prerequisite, then cost. Four sentences, none padding; the credit note earns its place because cost is not stated in any structured field.

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

Completeness3/5

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

For a heavy aggregation tool with no output schema, an agent still lacks a sense of response volume and structure (how large the prop/alternate-ladder payload is) and whether credits scale with result size. The contents are enumerated but the shape and scale are not.

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; the description adds that event_id comes from list_events or odds_board and that user_request should be one sentence describing the current task. That meaning is partly in the schema already, so the gain is modest but real.

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?

Opens with a specific verb and resource – everything for one game in one call – and enumerates the payload (period lines, every player prop with move since open, FanDuel alternate ladders, stat counts, biggest movers). The quoted example 'full odds and player props for Chiefs vs Bills' pins down the scope, which clearly separates it from narrower siblings such as line_move or prop_history.

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?

States when to use it (a weekly betting report or a research note on one game) and the required prerequisite step – find the event_id with list_events or odds_board. That routing names the alternatives explicitly, with no inference required.

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