Skip to main content
Glama

PropLine — Sports Betting Odds & Prop Resolution

by io.github.proplineapi
OverviewDiscussionsAdmin

Get player prop history

propline_get_player_history
Read-onlyIdempotent

Player prop history across recent games for one market. Returns each prior prop this player took with line, prices, resolution, actual value, is_main_line (the book's main line vs an alt-ladder rung) and line_moved_in_play. Pass main_line_only=true to drop alt rungs. Pro tier returns full data; free tier returns redacted resolution/actual_value with an upgrade pointer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax number of past games (default 20, max 100)
marketNoMarket key, e.g. 'pitcher_strikeouts' or 'player_points'
marketsNoDeprecated alias: the first market of a comma-separated list is used when `market` is omitted
sport_keyYes
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'
main_line_onlyNoOnly each book's main line (drops alt-ladder rungs). Omit for every line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / main_line_only
      Added value: +{
+  "description": "Only each book's main line (drops alt-ladder rungs). Omit for every line.",
+  "type": "boolean"
+}
    • addedInput schema / properties / market
      Added value: +{
+  "description": "Market key, e.g. 'pitcher_strikeouts' or 'player_points'",
+  "type": "string"
+}
    • changedInput schema / properties / markets / description
      Previous value: -"Comma-separated subset of markets (e.g. 'player_points,player_rebounds')"New value: +"Deprecated alias: the first market of a comma-separated list is used when `market` is omitted"
    • 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. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's safety burden is low. It adds meaningful behavior beyond annotations: field-level output details, main-line vs alt-ladder semantics, and free-tier redaction behavior with an upgrade pointer. There is no contradiction with annotations.

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?

Three sentences with no filler: purpose, return fields, and usage caveats are each covered in order. The conditional and tier notes are placed at the end without burying the main purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description compensates by listing the key returned fields and explaining tier-dependent redaction. Required parameters are covered by the schema, and the description gives enough top-level behavior for a read-only history tool. Minor details like ordering and exact date range are left unspecified, but 'recent games' plus the limit parameter provides adequate context.

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 83%, so the input schema already documents most parameters. The description adds useful context for main_line_only and clarifies the single-market nature of the call, but it does not substantially compensate for or explain parameters beyond what the schema already provides.

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?

The description starts with a specific object and scope: 'Player prop history across recent games for one market.' It then enumerates the returned fields, so an agent knows exactly what data this tool produces and can distinguish it from sibling history/game tools even without seeing their schemas.

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?

The first sentence establishes the intended use: fetching prop history for one market for a player. It also provides actionable conditional guidance ('Pass main_line_only=true to drop alt rungs') and tier-based expectations. It stops short of explicitly naming alternatives or when-not-to-use, so it doesn't earn a 5.

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

All PropLine — Sports Betting Odds & Prop Resolution toolsInspect
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.

Resources