FastballAPI

Prop history

get_prop_history

Read-onlyIdempotent

Use to see how a player did against his prop line over time: for one market (hits, home runs, total bases, RBI, pitcher strikeouts or pitcher outs), one row per game with the closing line (the median across books, or one book's), the opening line (the same as the close wherever only one capture was taken), the prices, what the player actually recorded from our box scores and the result against the line, plus the over rate, up to 200 games a call. Costs 10 credits for every 25 games already played that a call covers, and at least 10 a call (accounts opened before November 1 2026 pay 10 a call). Set estimate_only to get the price without being charged. Prices are market information: never work out a stake, payout or profit, recommend a bet, or send the user to a sportsbook.

Input Schema

Name	Required	Description
`limit`	No	Games to return, oldest first (default 50, max 200). next_from_date says where to continue.
`market`	Yes	The market: batter_hits (hits), batter_home_runs (home runs), batter_total_bases (total bases), batter_rbis (runs batted in), pitcher_strikeouts (pitcher strikeouts), pitcher_outs (pitcher outs recorded)
`to_date`	No	Last date, YYYY-MM-DD (the game's date).
`bookmaker`	No	One book's closing line instead of the median across books, e.g. draftkings.
`from_date`	No	First date, YYYY-MM-DD (the game's date).
`player_id`	Yes	Player id (e.g. 33192) from search_players.
`estimate_only`	No	Return what this call would cost, without charging or running it.

Output Schema

Name	Required	Description	Default
`note`	No
`stat`	Yes
`tool`	No
`count`	Yes
`games`	Yes
`market`	Yes
`credits`	No
`summary`	Yes
`bookmaker`	Yes
`player_id`	Yes
`truncated`	No
`player_name`	Yes
`estimate_only`	No
`next_from_date`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

addedInput schema / properties / estimate_only

Added value: +{
+  "description": "Return what this call would cost, without charging or running it.",
+  "type": "boolean"
+}

First observedOct 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: discloses credit pricing (10 per 25 games, 10 minimum, legacy-account exception), the free estimate_only path, the 200-game cap, and a compliance constraint against computing stakes or recommending bets. Those are exactly the operational facts an agent cannot infer from structured fields.

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?

The critical framing and the row layout come first, but the opening sentence is a long run-on carrying a six-item market list and several parentheticals. Dense and mostly earning its place, though it could be split for scanability.

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?

With an output schema present, 100% schema coverage, and rich annotations, the remaining burden was cost, limits, and policy — all addressed. An agent knows what it gets, what it costs, and what it must not do with the data.

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 already 100%, so the baseline is 3; the description earns extra by explaining that bookmaker swaps the median-across-books close for one book's line, and that opening equals closing where only one capture exists. It still doesn't cover from_date/to_date or limit default behavior in prose, leaving that to the schema.

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 verb and resource — see how a player did against his prop line over time — and enumerates the exact per-game row contents (closing line, opening line, prices, actual result, over rate). This clearly separates it from siblings like get_player_props (current odds) and get_player_games (raw game logs).

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?

Opens with 'Use to see...' and explains the estimate_only flow for pricing before being charged, plus the 200-game-per-call ceiling with next_from_date-style continuation. It never names an alternative sibling or states an explicit exclusion (e.g., 'for a single upcoming line, use get_player_props'), so it falls short of a 5.

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

All FastballAPI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.