Skip to main content
Glama

Alt lines

get_alt_lines
Read-onlyIdempotent

Use for alternate puck lines and totals by sportsbook: every point on each book's ladder with its price (e.g. -2.5 at +250, over 7.5 at +160), for one game. Held for NHL games from the 2023-24 season on, from up to five books (Pinnacle, Bovada, BetMGM and DraftKings, FanDuel on some). Games before Nov 12 2026 were captured once shortly before puck drop, 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 puck lines (point is that side's puck line) 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 nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl, ahl, ushl.
marketNoOne market (default both).
game_idYesGame id, e.g. 2025020150 (from get_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.5/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent read, and the description adds real context beyond them: the historical capture cadence (single pre-puck-drop snapshot before Nov 12 2026, up to three daily captures after), the default closing-ladder behavior, the 10-credit cost, and the no-wagering disclaimer. These are exactly the operational facts an agent needs and cannot get from structured fields.

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 and scope are front-loaded and nearly every clause carries information (coverage window, cost, default, alternative). It is dense to the point of being a run-on, and the stray 'side' explanation spends words on something the schema does not expose.

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 an output schema present, return shape need not be explained, and the description still covers coverage, defaults, cadence, cost, and the sibling alternative. The one gap is the 'side' reference that does not map to any parameter, leaving a small inconsistency an agent may trip over.

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 coverage is 100%, so all five parameters are already documented and the baseline is 3. The description does add meaning for snapshot_type ('its last before the start') and clarifies the book set, but it also describes a 'side' parameter (home/away, over/under) that does not exist in the input schema, which muddies rather than clarifies parameter semantics.

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 opens with a specific verb-and-resource statement: alternate puck lines and totals per sportsbook, with concrete examples of ladder points and prices. It scopes the resource to one game and explicitly routes the main line elsewhere ('For the main line use get_odds'), so it is distinguishable from get_odds and get_market_odds 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?

It names the alternative tool and the condition that selects it ('For the main line use get_odds'), and states coverage boundaries: NHL from 2023-24 onward, up to five books, games not yet priced return nothing. An agent knows both when this applies and when it does not.

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.