Skip to main content
Glama

Prop history

get_prop_history
Read-onlyIdempotent

Use to see how a player did against his prop line over time: for one market (points, goals, assists, shots on goal, blocked shots, goalie saves, power-play points, or anytime or first goal scorer), 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; no tool places, accepts or tracks wagers.

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": {
      "player_id": "<player_id>",
      "market": "<market>"
    },
    "name": "get_prop_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoGames to return, oldest first (default 50, max 200). next_from_date says where to continue.
marketYesThe market: player_points (points), player_goals (goals), player_assists (assists), player_shots_on_goal (shots on goal), player_blocked_shots (blocked shots), player_total_saves (goalie saves), player_goal_scorer_anytime (anytime goal scorer (over = scores)), player_power_play_points (power-play points), player_goal_scorer_first (first goal scorer (over = scores the game's first goal))
to_dateNoLast date, YYYY-MM-DD (the game's date).
bookmakerNoOne book's closing line instead of the median across books, e.g. draftkings.
from_dateNoFirst date, YYYY-MM-DD (the game's date).
player_idYesPlayer id (e.g. 8478402) from search_players.
estimate_onlyNoReturn what this call would cost, without charging or running it.

Output Schema

NameRequiredDescriptionDefault
noteNo
statYes
toolNo
countYes
gamesYes
marketYes
creditsNo
summaryYes
bookmakerYes
player_idYes
truncatedNo
player_nameYes
estimate_onlyNo
next_from_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / market / description
      Previous value: -"The market: player_points (points), player_goals (goals), player_assists (assists), player_shots_on_goal (shots on goal), player_blocked_shots (blocked shots), player_total_saves (goalie saves), player_goal_scorer_anytime (anytime goal scorer (over = scores))"New value: +"The market: player_points (points), player_goals (goals), player_assists (assists), player_shots_on_goal (shots on goal), player_blocked_shots (blocked shots), player_total_saves (goalie saves), player_goal_scorer_anytime (anytime goal scorer (over = scores)), player_power_play_points (power-play points), player_goal_scorer_first (first goal scorer (over = scores the game's first goal))"
    • changedInput schema / properties / market / enum
      Previous value: -[
      -  "player_points",
      -  "player_goals",
      -  "player_assists",
      -  "player_shots_on_goal",
      -  "player_blocked_shots",
      -  "player_total_saves",
      -  "player_goal_scorer_anytime"
      -]New value: +[
      +  "player_points",
      +  "player_goals",
      +  "player_assists",
      +  "player_shots_on_goal",
      +  "player_blocked_shots",
      +  "player_total_saves",
      +  "player_goal_scorer_anytime",
      +  "player_power_play_points",
      +  "player_goal_scorer_first"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / estimate_only
      Added value: +{
      +  "description": "Return what this call would cost, without charging or running it.",
      +  "type": "boolean"
      +}
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantial context beyond that. It discloses the cost model (10 credits per 25 games, minimum 10), the estimate_only escape hatch, the 200-game cap, and the fact that no wagering is placed or tracked.

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 purpose is front-loaded and the cost details are relevant, so most sentences earn their place. The paragraph is dense and somewhat run-on, but it avoids filler and keeps essential caveats such as pricing and no-wagering disclosure.

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?

This is a fairly complex tool with pricing, output shape, market selection, and an estimate mode, and the description covers the critical behavioral facts. The output schema exists, so return values need not be fully explained, and the schema handles pagination details like next_from_date. Nothing essential for correct invocation is missing.

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 description coverage is 100%, so the schema already explains every parameter, including the market enum, bookmaker, dates, player_id, and estimate_only. The description restates some of that meaning, such as median versus one book's closing line, but adds little parameter syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

The description states a specific verb and resource: seeing how a player performed against a prop line over time, one row per game. It clearly defines the scope and output contents. It does not explicitly name or distinguish itself from sibling tools such as get_prop_backtest, so it falls short of a 5 on sibling differentiation.

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?

It gives a clear usage cue: 'Use to see how a player did against his prop line over time,' and explains using estimate_only to avoid charges. It does not explicitly say when not to use it or name alternatives, so it is clear context without exclusions.

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.