Skip to main content
Glama

Prop Line Shopper: Every Book Side by Side (Pro)

line_shop
Read-onlyIdempotent

Use this when the user asks where a player prop's line or price differs between sportsbooks today, which book has the best over or under price, or which props the books disagree on. Returns one stat's props of the day (NBA) or the week ahead (NFL): per player every book's main line with its over and under prices, the best price on each side, the lowest and highest line and whether the books split on it, with the books on the board in vendors. Requires Keel Stats Pro; the answer says so when the account has none. A research table: no book is recommended. Not for a player's history against the line: use line_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": {
      "league": "<league>"
    },
    "name": "line_shop"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional NBA game day (YYYY-MM-DD). Default: the next day with props.
statNoOptional stat code (NBA: "pts", "reb", "ast", "tpm", "pra"…; NFL: "passing_yards", "receiving_yards"…). Default: the board's first.
limitNoRows to return (default 20, at most 30).
leagueYesLeague ("nba" or "nfl").
game_idNoOptional numeric game ID: that game's props only.
player_idNoOptional numeric player ID: his row only.
split_onlyNoOptional: only the props where the books' lines differ.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent, closed-world read, so the bar is lower; the description still adds real value by disclosing the Keel Stats Pro entitlement gate and the failure message when the account lacks it, plus the framing that this is a research table with no book recommended. It does not mention row-cap behavior or result ordering beyond what the schema states, which keeps it short of a 5.

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?

Front-loads the use case, then the return shape, then the entitlement caveat, then the sibling exclusion — a sensible ordering with no filler sentences. The prose is dense with semicolons and clauses rather than cleanly separated, which costs readability slightly but nothing is wasted.

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 carries the return-value burden and does so by enumerating the returned fields (per-book main line, over/under prices, best price per side, low/high line, split flag, `vendors` board list). Combined with the entitlement note and the explicit sibling exclusion, an agent has everything needed to call it correctly.

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; the description adds meaning beyond the schema by tying `league` to the time window (NBA = props of the day, NFL = week ahead) and by explaining that `vendors` lists the books on the board. It also implicitly motivates `split_only` via the 'books split on it' language, though it never names that parameter directly.

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?

Names a specific resource and verb scope: returns one stat's props of the day (NBA) or week ahead (NFL) with per-player, per-book main lines, over/under prices, best price per side, and high/low line with split status. It explicitly contrasts with the sibling line_history, so an agent can route between them without opening either schema.

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 three concrete trigger conditions (where a prop's line or price differs between books, which book has the best over/under price, which props books disagree on) and states an explicit exclusion: 'Not for a player's history against the line: use line_history.' Both the when and the when-not are covered.

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