Skip to main content
Glama

get_player_props

Read-only

Read pregame player props at every book GetOdds carries for one sport, merged per player, stat and game day: FanDuel, DraftKings, BetRivers, Pinnacle and Novig prices (American odds; Novig is the exchange ask), PrizePicks, Underdog and DK Pick6 lines, the median line, best over and under, a no-vig fair price and pick’em gaps. Available to every key. Quotes with history=true work with get_prop_history.

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": {
      "sport": "<sport>"
    },
    "name": "get_player_props"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
statNo
booksNoComma list of fanduel, draftkings, betrivers, pinnacle, novig, prizepicks, underdog, pick6
limitNo
sportYes
offsetNo
playerNo
min_booksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuine behavioral value by enumerating the merged output fields (median line, best over/under, no-vig fair price, pick'em gaps) and flagging Novig as an exchange ask rather than a book price. It stops short of disclosing pagination behavior, book-availability failures, or the fact that 'history=true' is not an exposed parameter — a notable gap given the low schema coverage.

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?

Purpose is front-loaded in the first clause, and the book enumeration, while long, is load-bearing information rather than filler. The second sentence is a compact pointer to a sibling. A slightly shorter framing of the odds-type list would tighten it without losing meaning.

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?

With no output schema, the description correctly takes on the job of describing the returned fields and does so in useful detail, including odds format. It is adequately complete for an 8-parameter read tool, with the remaining shortfall concentrated in pagination and filter-parameter semantics rather than in what the tool returns.

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 only 13% (only `books` is documented), so the description carries most of the burden. It implicitly maps to several parameters — one sport (`sport`), the merge keys (`player`, `stat`, `date`), and the book list — and its mention of 'merged' hints at `min_books`. But limit, offset, min_books semantics, the date format, and the stat-name pattern are left entirely to the schema, so compensation is partial.

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 leads with a specific verb and resource ('Read pregame player props') and pins down scope: every book GetOdds carries, one sport, merged per player/stat/game day. 'Pregame' excludes live props and the explicit handoff to get_prop_history separates it from the history tool, so an agent can distinguish it from siblings without opening a schema.

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 establishes the usage context clearly — one sport, pregame props, and that history-backed quotes continue via get_prop_history. What it lacks is any explicit exclusion or prerequisite (e.g. how to pick this over the market/odds tools when a player name is unknown), so the guidance is clear but not complete.

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.