Skip to main content
Glama

The Odds Gap

Player Prop

player_prop
Read-onlyIdempotent

One player's prop: the line the market is at and the highest price we saw on each side, with the scan time. The player must be on our props board. Prices may have moved since the scan.

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": "<player>"
    },
    "name": "player_prop"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineNoThe line the person named, if they named one.
sideNoover, under, yes or no.
booksNoThe books this person actually has. Omit for the default set.
marketNoThe prop market key, e.g. player_receptions or pitcher_strikeouts. Omit to be told what the board has for that player.
playerYesThe player's name as the person typed it.

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the tool produced an answer.
cardNoThe same answer, structured, when there is one. A figure in it keeps its field name (edge_pct, ev_pct) and carries a plain label beside it: "label": "Above Fair" (percent above our fair price, not expected profit) or "Above Break-Even" for a middle.
pageYesThe matching page on theoddsgap.com.
toolNo
as_ofNoWhen the prices were scanned, Eastern Time.
staleNoTrue when that scan is older than usual for our hourly snapshot.
answerYesThe answer in plain sentences.
optionsNoWhen the question could mean more than one thing: whole questions to ask again with.
warningsNo
state_noteNoWhere to check what is legal for you.
decline_kindNoSet when the question is one we do not answer, and which kind.
free_left_todayNo
responsible_gamblingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / card / description
      Previous value: -"The same answer, structured, when there is one."New value: +"The same answer, structured, when there is one. A figure in it keeps its field name (edge_pct, ev_pct) and carries a plain label beside it: \"label\": \"Above Fair\" (percent above our fair price, not expected profit) or \"Above Break-Even\" for a middle."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is a safe, idempotent, non-destructive, closed-world read. The description adds useful behavioral context beyond those annotations: the result reflects a prior scan, prices may be stale, and the player must exist on the props board.

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?

The description is short, front-loaded, and contains no wasted sentences. It first describes the output, then the eligibility constraint, then the freshness caveat in a logical order.

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?

Given the low complexity, complete input schema, existing output schema, and safety annotations, the description covers the essentials an agent needs: what is returned, the board-membership prerequisite, and the staleness caveat. A minor gap remains around how the side and line parameters interact with the 'each side' result, but the definition is otherwise complete.

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 parameters are already documented well by the schema. The description does not add parameter-level meaning beyond reinforcing that the player must be on the board and that results include each side, leaving the roles of line, side, books, and market to the schema.

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 states a precise resource, 'one player's prop,' and specifies the returned content: the market line, the highest price seen on each side, and the scan time. This clearly distinguishes it from team-level odds siblings such as game_lines or futures_odds without needing to name them.

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?

The description gives a concrete prerequisite, 'The player must be on our props board,' and warns that prices may have moved since the scan. However, it does not explicitly state when to use this tool versus alternatives such as game_lines, futures_odds, or other odds tools, so usage routing is only implied by the resource scope.

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.

Resources