Skip to main content
Glama

PropLine — Sports Betting Odds & Prop Resolution

Get player game log / H2H

propline_get_player_games
Read-onlyIdempotent

A player's recent games with every raw box-score stat per game — one call instead of one request per event. Use this to answer 'how has X actually performed lately?' and to build L5/L10/L20, season splits and head-to-head yourself. Pass opponent for H2H (accepts a full name, nickname or abbreviation — 'Boston Red Sox', 'Red Sox', 'BOS'); the limit applies AFTER that filter, so opponent + limit=10 means the last 10 MEETINGS, not the Boston games among the last 10 games. H2H is not capped to the current season. IMPORTANT: this is the raw box-score archive, NOT graded-prop history — it covers every game with a box score on file, including games no sportsbook priced, so a 'last 10 games' window here really is the last 10 games (one built from propline_get_player_trends silently skips unpriced games). It carries no line, price or grade; use propline_get_player_trends for hit rates against a posted line. player_team/opponent/is_home are null when the player's side can't be identified, and always for individual sports (tennis, golf, UFC) — report them as unknown rather than guessing. Accepts a player_id in place of the name; the response carries player_id (null when the player has none yet).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoGames to return, 1-100. Default 20.
opponentNoOptional head-to-head filter — team name, nickname or abbreviation.
sport_keyYes
stat_typeNoOptional comma-separated stat names to return; omit for all. Vocabulary is per-sport.
player_nameYesPlayer name as it appears in box scores — e.g. 'Aaron Judge', 'Nikola Jokic' — or a player_id from propline_search_players, e.g. 'mlb:592450'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / player_name / description
      Previous value: -"Player name as it appears in box scores — e.g. 'Aaron Judge', 'Nikola Jokic'"New value: +"Player name as it appears in box scores — e.g. 'Aaron Judge', 'Nikola Jokic' — or a player_id from propline_search_players, e.g. 'mlb:592450'"
  2. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds critical behavior beyond them: limit is applied AFTER the opponent filter, H2H is not capped to the current season, unpriced games are included (unlike trends), and fields are null for individual sports or unknown sides.

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?

Long but dense and front-loaded: purpose first, then the usage routing, then the H2H, raw-archive and null-field caveats. Every sentence carries distinct information with no filler.

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 no output schema, the description compensates by describing what is returned (per-game raw box-score stats, player_id in the response, null-when-unknown fields) and the constraints on filtering. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 80%, but the description adds semantics the schema lacks: opponent accepts full name/nickname/abbreviation, limit is post-filter, player_id is accepted in place of the name, and the null-field behavior of player_team/opponent/is_home is explained.

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+resource ('a player's recent games with every raw box-score stat per game') and explicitly distinguishes itself from sibling tools like propline_get_player_trends and propline_get_player_history by contrasting raw box-score archive vs graded-prop history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use ('how has X actually performed lately?', building L5/L10/L20, splits, H2H) and when-not ('use propline_get_player_trends for hit rates against a posted line'). The opponent/limit interaction warning is a concrete usage rule, not vague guidance.

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.