Skip to main content
Glama

FastballAPI

Player props

get_player_props
Read-onlyIdempotent

Use for player prop lines by sportsbook: over/under on hits, home runs, total bases, RBI, pitcher strikeouts and pitcher outs, from May 2023 (DraftKings, FanDuel, BetMGM, ESPN BET, Pinnacle and others). Pass game_id for every player's props in one game, or player_id with from_date (and to_date) for one player across games (up to 100). A game costs 10 credits before it starts and 20 once it has (accounts opened before October 30 2026 pay 10 for every game). Returns the closing line by default (the last before the game starts) or the opening line, with each book's over and under prices. Each row has captured_at, scheduled_start and minutes_before_scheduled_start (negative when captured after the scheduled start); a row is kept when it was captured before the sportsbooks' listed start, which in the NBA is usually about 10 minutes after the scheduled one, so filter on minutes_before_scheduled_start > 0 for a strictly before-schedule backtest. Outside football the archive mostly holds one pre-game capture per line, so the opening and closing lines are usually the same; the opening line differs only where a second capture was taken (live capture from October 2026, and wherever else it is held). Set estimate_only to get the price without being charged. Prices are market information; no tool places, accepts or tracks wagers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_player_props"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketNoOne 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)
game_idNoGame id: every player's props for that game.
to_dateNoWith player_id: last date (default: no end), YYYY-MM-DD (the game's date).
bookmakerNoBookmaker key, e.g. draftkings, fanduel, pinnacle.
from_dateNoWith player_id: first date, YYYY-MM-DD (the game's date).
player_idNoPlayer id (e.g. 33192) from search_players. With from_date: that player's props across games.
estimate_onlyNoReturn what this call would cost, without charging or running it.
snapshot_typeNoclosing (default): the last line before the game starts. opening: the first one captured, which is the same capture as the close wherever only one was taken.

Output Schema

NameRequiredDescriptionDefault
noteNo
toolNo
countNo
gamesNo
propsNo
creditsNo
estimate_onlyNo
snapshot_typeNo
next_from_dateNo
credits_per_gameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / props / items / properties / minutes_before_scheduled_start
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / props / items / properties / scheduled_start
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / snapshot_type / description
      Previous value: -"closing (default): the last line before the game starts. opening: the first one captured."New value: +"closing (default): the last line before the game starts. opening: the first one captured, which is the same capture as the close wherever only one was taken."
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/non-destructive; the description adds substantial context beyond that: 10 credits before a game and 20 after (with legacy pricing), estimate_only avoids the charge, default snapshot is closing, and no tool places or tracks wagers. It also discloses the non-obvious retention rule (row kept if captured before the sportsbook's listed start, ~10 min after scheduled start in the NBA) and the caveat that opening and closing lines are usually identical outside football.

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?

Front-loaded with the purpose, then access patterns, then cost/capture semantics. It is dense and long, and the dated pricing/capture carve-outs ('accounts opened before October 30 2026', 'live capture from October 2026') add noise, but nearly every sentence carries decision-relevant information.

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 an 8-parameter, zero-required tool with credit costs and subtle timestamp semantics, the description covers access patterns, pricing, snapshot behavior, row fields (captured_at, scheduled_start, minutes_before_scheduled_start) and a recommended filter for backtests. An output schema exists, so return shape need not be spelled out further.

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, and the description still adds meaning: the 100-row cap on player_id queries, the default closing snapshot, and the fact that estimate_only returns a price without being charged. Minor gap: the market enum and bookmaker keys are left entirely to the schema.

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?

States a specific verb+resource ('player prop lines by sportsbook') and enumerates the covered markets (hits, home runs, total bases, RBI, strikeouts, outs), so an agent knows exactly what data comes back. It does not name sibling tools such as get_prop_history or get_prop_movement to delineate boundaries, which keeps it short of a 5.

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 access patterns: game_id for a whole game, or player_id with from_date/to_date for one player across games (capped at 100), plus estimate_only for a free price check and snapshot_type for opening vs closing. The when-to-use logic is clear, but there is no explicit 'use X instead when...' routing to related prop tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.