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 (anytime, first or last goalscorer, to be carded, shots on target, shots or assists: one row per match with the closing price and what he recorded), 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. over_odds is the Yes price; result is over when he scored, under when he played and did not, and null when he was not in the squad or on the pitch (a void). 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.
leagueNoLeague. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl.
marketYesThe market: player_goal_scorer_anytime (anytime goalscorer (over = scores)), player_shots_on_target (shots on target), player_shots (shots), player_assists (assists), player_first_goal_scorer (first goalscorer (over = scores the match's first goal)), player_last_goal_scorer (last goalscorer (over = scores the match's last goal)), player_to_receive_card (to be carded (over = shown a yellow or red card))
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. 280555) 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_goal_scorer_anytime (anytime goalscorer (over = scores)), player_shots_on_target (shots on target), player_shots (shots), player_assists (assists)"New value: +"The market: player_goal_scorer_anytime (anytime goalscorer (over = scores)), player_shots_on_target (shots on target), player_shots (shots), player_assists (assists), player_first_goal_scorer (first goalscorer (over = scores the match's first goal)), player_last_goal_scorer (last goalscorer (over = scores the match's last goal)), player_to_receive_card (to be carded (over = shown a yellow or red card))"
    • changedInput schema / properties / market / enum
      Previous value: -[
      -  "player_goal_scorer_anytime",
      -  "player_shots_on_target",
      -  "player_shots",
      -  "player_assists"
      -]New value: +[
      +  "player_goal_scorer_anytime",
      +  "player_shots_on_target",
      +  "player_shots",
      +  "player_assists",
      +  "player_first_goal_scorer",
      +  "player_last_goal_scorer",
      +  "player_to_receive_card"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / market / description
      Previous value: -"The market: player_goal_scorer_anytime (anytime goalscorer (over = scores))"New value: +"The market: player_goal_scorer_anytime (anytime goalscorer (over = scores)), player_shots_on_target (shots on target), player_shots (shots), player_assists (assists)"
    • changedInput schema / properties / market / enum
      Previous value: -[
      -  "player_goal_scorer_anytime"
      -]New value: +[
      +  "player_goal_scorer_anytime",
      +  "player_shots_on_target",
      +  "player_shots",
      +  "player_assists"
      +]
  3. 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"
      +}
  4. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantial behavior beyond them: a credit cost model (10 credits per 25 games played, minimum 10 per call, with a grandfathering note), a free estimate_only path, and explicit result semantics where over means he scored, under means he played without scoring, and null means void. It also states that prices are market information and that no tool places, accepts, or tracks wagers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, but the body is effectively one very long sentence dense with nested parentheses, which makes it hard to scan. Some content duplicates the schema, such as the 200-game cap and the market list, so not every clause earns its place.

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 tool with an output schema, the description covers what an agent needs before calling: market scope, date and bookmaker behavior, row semantics, cost and the free estimate path, and void handling. Return-column explanation is present but not required, so nothing material is missing.

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 the baseline is 3, but the description still adds real meaning: over_odds is identified as the Yes price, the closing line is the median across books unless one bookmaker is supplied, the opening line equals the close where only one capture exists, and limit is bounded at up to 200 games per call. These clarifications go beyond the field descriptions in 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?

The description names a specific verb and resource: per-game history of a player's results against his prop line for one market, with closing line, opening line, prices, and actual recorded output. It enumerates the supported markets, which makes the resource unambiguous. It does not explicitly distinguish itself from siblings such as get_prop_backtest or get_prop_movement, so it stops 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 Guidelines3/5

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

Usage is implied by the opening 'Use to see how a player did against his prop line over time,' and it gives a concrete operational hint: set estimate_only to get the price without being charged. However, there is no explicit when-not clause and no named alternative (e.g. the backtest or movement tools) that would tell an agent which sibling to pick for which question.

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.