Skip to main content
Glama
fanduelapi-mcp

fanduelapi-mcp

prop_history

Retrieve one prop's full recorded history—line moves, price moves, suspensions with timestamps, and a move summary—oldest first, to trace how its odds changed over time.

Instructions

Every recorded state of one prop, oldest first: each line move, price move and suspension with its time, plus the move summary. Use it after list_props or line_move when you need the full path, not just open and current. A default call costs 10 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": {
      "prop_id": "<prop_id>",
      "user_request": "<user_request>"
    },
    "name": "prop_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
prop_idYesOne prop's id from list_props.
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.2/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 burden and does well: it discloses return ordering, the content of each entry, and a concrete cost ('a default call costs 10 credits') with a pricing link. It does not mention volume limits or what happens to very long histories, 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?

Two sentences, each earning its place: the first defines the output, the second routes usage and discloses cost. Front-loaded with the payload description before the guidance.

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?

No output schema exists, so the description correctly spends words describing what each returned entry contains, and it adds cost transparency. It is complete for a two-parameter read tool; only pagination/volume behavior for large histories is unaddressed.

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 coverage is 100%, so both parameters are already fully documented in the schema. The description only implies prop_id via 'one prop' and adds no meaning to user_request, so baseline 3 is correct.

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?

States a specific resource (one prop's recorded states) with the exact ordering ('oldest first') and enumerates what each line contains (line move, price move, suspension, time, move summary). It also distinguishes itself from siblings by contrasting 'the full path' with 'just open and current' from list_props/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 Guidelines4/5

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

Gives explicit sequencing ('use it after list_props or line_move') and a selection condition ('when you need the full path, not just open and current'). It stops short of stating when not to call it in absolute terms, but the contrast with line_move is enough to route most agents.

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