Skip to main content
Glama

DunkAPI

Alt lines

get_alt_lines
Read-onlyIdempotent

Use for alternate spreads and totals by sportsbook: every point on each book's ladder with its price (e.g. -8.5 at +240, over 230.5 at +165), for one game. Held for the NBA, the WNBA and men's college basketball from the 2023-24 season on, from up to five books (DraftKings, Pinnacle, Bovada and BetMGM on nearly every game, FanDuel on some). Games before Nov 12 2026 were captured once shortly before the start, so their opening and closing ladders are the same; from Nov 12 2026 upcoming games are captured up to three times a day before the start. Games not yet priced have none. Returns each book's closing ladder by default (its last before the start) or its opening one. side is home or away for spreads (point is that side's spread) and over or under for totals. For the main line use get_odds. 10 credits. Prices are market information; no tool places, accepts or tracks wagers.

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": {
      "game_id": "<game_id>"
    },
    "name": "get_alt_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague. Defaults to nba. One of: nba, wnba, ncaam, ncaaw, nbl.
marketNoOne market (default both).
game_idYesGame id, e.g. 401585183 (from list_games or get_schedule).
bookmakerNoOne bookmaker key, e.g. draftkings, fanduel.
snapshot_typeNoClosing (default) or opening ladder.

Output Schema

NameRequiredDescriptionDefault
noteNo
countYes
linesYes
leagueYes
game_idYes
snapshot_typeYes

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 readOnly, non-destructive, idempotent and closed-world, and the description goes well beyond them: snapshot cadence (pre-Nov-12-2026 games captured once shortly before start, so opening and closing ladders are identical; later games captured up to three times a day), default return (closing ladder), cost of 10 credits, and the explicit note that no tool places or tracks wagers. The only gap is that it does not describe pagination or ordering of the returned ladder.

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-loaded with purpose and example prices before the coverage and cadence details. It is dense but nearly every sentence carries operational information; the capture-cadence sentence is long and parenthetical-heavy, but it explains why opening and closing may be identical, which is not waste.

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?

Given five parameters, an output schema that already documents return shape, and rich annotations, the description supplies exactly what is missing: coverage boundaries, capture timing, defaults, cost, and the main-line alternative. An agent could decide whether to call it and interpret the result without further guidance.

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, but the description adds real meaning: it explains that snapshot_type's closing ladder is the book's last price before the start (versus opening), which the schema does not spell out, and it defines how to read side and point (home/away for spreads, over/under for totals). Bookmaker and league defaults are largely left 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?

States a specific verb-and-resource combination: alternate spreads and totals by sportsbook, every point on each book's ladder with its price, for one game, with a concrete example of a ladder rung. It explicitly contrasts itself with the main-line tool ("For the main line use get_odds"), so an agent can separate it from get_odds and get_market_odds 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 Guidelines5/5

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

Names the alternative (get_odds) and the condition that selects it (you want the main line). It also bounds usage with concrete coverage rules: which leagues, which seasons (2023-24 onward), which books, and the note that unpriced games return nothing, so the agent knows when this tool will silently be empty.

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.