Skip to main content
Glama

Odds

get_odds
Read-onlyIdempotent

Use when checking betting lines. Pass game_id for one game (10 credits): moneyline, puck line and total by bookmaker, opening and closing. Or pass season (optionally with team) for a whole season of closing lines in one call, with final scores, at 10 credits per game returned (a full season is ~13,700 credits, a team-season ~820), 100 games a page by default (up to 500). Each book's line is an array in the order given by columns. Set estimate_only to get the price without being charged. Every game from 2019-20 on (and part of the 2019 playoffs): about 16 to 18 books a game from 2020-21 to 2023-24, about 6 in 2019-20, 8 in 2024-25 and 2025-26 (60+ on about 300 games in 2025-26), with all_books; a season answer defaults to the four main books. A season those four do not carry (2019-20) returns every book it has. Each line carries a source field (one value for opening and closing lines from August 2020, another for final per-book lines); a season answer lists each game's sources. Prices are market information; no tool places, accepts or tracks wagers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoWith season: only this team's games (abbreviation, e.g. BUF).
limitNoWith season: games per page (default 100, max 500).
offsetNoWith season: page offset; use next_offset from the previous page.
seasonNoSeason for a whole season of lines, e.g. 2025-26 or 20252026. Used when game_id is not set.
game_idNoNHL game ID (e.g. 2025020887). Omit and pass season for a whole season.
all_booksNoWith season: every book held (16 to 18 a game from 2020-21 to 2023-24, 8 in 2024-25, more than 60 on about 300 games in 2025-26) instead of DraftKings, FanDuel, BetMGM and ESPN BET.
bookmakerNoFilter by bookmaker key (e.g. draftkings, fanduel, betmgm). Lowercase.
estimate_onlyNoReturn what this call would cost, without charging or running it.
snapshot_typeNoopening (game-day morning; for a game not yet played, the latest morning line) or closing (final pre-game). Single game: default every snapshot held, including first (each book's first posted line, from October 2026). Season: default closing.

Output Schema

NameRequiredDescriptionDefault
noteNo
oddsNo
toolNo
countNo
gamesNo
seasonNo
columnsNo
creditsNo
game_idNo
away_teamNo
game_dateNo
home_teamNo
next_offsetNo
total_gamesNo
estimate_onlyNo
snapshot_typeNo
bookmaker_countNo
credits_per_gameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / snapshot_type / description
      Previous value: -"opening (game-day morning; for a game not yet played, the latest morning line) or closing (final pre-game). Single game: default both. Season: default closing."New value: +"opening (game-day morning; for a game not yet played, the latest morning line) or closing (final pre-game). Single game: default every snapshot held, including first (each book's first posted line, from October 2026). Season: default closing."
  2. Changed1 schema field changed
    • changedInput schema / properties / all_books / description
      Previous value: -"With season: every book held (12-14 a game from 2020-21 to 2023-24, more than 60 on about 300 games in 2025-26) instead of DraftKings, FanDuel, BetMGM and ESPN BET."New value: +"With season: every book held (16 to 18 a game from 2020-21 to 2023-24, 8 in 2024-25, more than 60 on about 300 games in 2025-26) instead of DraftKings, FanDuel, BetMGM and ESPN BET."
  3. Changed1 schema field changed
    • changedInput schema / properties / all_books / description
      Previous value: -"With season: every book held (12-14 a game from 2020-21 to 2023-24, 60+ from 2025-26) instead of DraftKings, FanDuel, BetMGM and ESPN BET."New value: +"With season: every book held (12-14 a game from 2020-21 to 2023-24, more than 60 on about 300 games in 2025-26) instead of DraftKings, FanDuel, BetMGM and ESPN BET."
  4. Changed1 schema field changed
    • addedOutput schema / properties / note
      Added value: +{
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / all_books / description
      Previous value: -"With season: every book held (60+ from 2025-26) instead of DraftKings, FanDuel, BetMGM and ESPN BET."New value: +"With season: every book held (12-14 a game from 2020-21 to 2023-24, 60+ from 2025-26) instead of DraftKings, FanDuel, BetMGM and ESPN BET."
  6. Changed1 schema field changed
    • changedInput schema / properties / snapshot_type / description
      Previous value: -"opening (game-day morning) or closing (final pre-game). Single game: default both. Season: default closing."New value: +"opening (game-day morning; for a game not yet played, the latest morning line) or closing (final pre-game). Single game: default both. Season: default closing."
  7. Changed21 schema fields changed
    • addedInput schema / properties / all_books
      Added value: +{
      +  "description": "With season: every book held (60+ from 2025-26) instead of DraftKings, FanDuel, BetMGM and ESPN BET.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / estimate_only
      Added value: +{
      +  "description": "Return what this call would cost, without charging or running it.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / game_id / description
      Previous value: -"NHL game ID (e.g. 2025020887)"New value: +"NHL game ID (e.g. 2025020887). Omit and pass season for a whole season."
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "With season: games per page (default 100, max 500).",
      +  "maximum": 500,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "With season: page offset; use next_offset from the previous page.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / season
      Added value: +{
      +  "description": "Season for a whole season of lines, e.g. 2025-26 or 20252026. Used when game_id is not set.",
      +  "type": "string"
      +}
    • changedInput schema / properties / snapshot_type / description
      Previous value: -"Filter by snapshot type: opening (game-day morning lines) or closing (final pre-game lines). Default returns both."New value: +"opening (game-day morning) or closing (final pre-game). Single game: default both. Season: default closing."
    • addedInput schema / properties / team
      Added value: +{
      +  "description": "With season: only this team's games (abbreviation, e.g. BUF).",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "game_id"
      -]
    • addedOutput schema / properties / columns
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / count
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / credits
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / credits_per_game
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / estimate_only
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / games
      Added value: +{
      +  "items": {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / next_offset
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / season
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / snapshot_type
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / tool
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / total_games
      Added value: +{
      +  "type": "number"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "game_id",
      -  "home_team",
      -  "away_team",
      -  "game_date",
      -  "odds",
      -  "bookmaker_count"
      -]
  8. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, but the description adds genuinely non-inferable behavior: credit pricing per mode (~13,700 for a full season, ~820 for a team-season), that estimate_only returns the price without charging, that all_books overrides the four-book default, that 2019-20 has no four-book answer, and that lines carry a source field with different values for historical periods.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The intent is front-loaded ('Use when checking betting lines') and each mode is introduced in order, but the middle of the description degenerates into a long run-on cataloguing book counts by season (16-18, 6, 8, 60+, ~300 games) that is hard to parse and partly duplicates the all_books schema text. That coverage nuance could be one clause instead of several.

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?

Despite nine parameters, two modes, and a non-trivial cost model, the description covers cost, defaults, coverage limits by season, pagination behavior, the source field, and the key constraint that it is market data only and no wager is placed or tracked. An output schema exists, and the description still usefully sketches the per-book array shape, so nothing an agent needs to call it correctly is missing.

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: which parameter combination selects which mode, the effective default of four main books for a season answer versus schema-silent behavior, that a team-season costs far less than a full season, and the meaning of the source field. Some overlap with the schema (paging limits, all_books book counts) keeps it off 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and what is returned: 'moneyline, puck line and total by bookmaker, opening and closing', with two distinct modes (single game via game_id, whole season via season). It is clearly not a player-prop or line-movement tool. It stops short of naming a sibling (e.g. get_market_odds or get_line_movement) as the alternative, so it does not fully hit the 5 bar.

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?

'Use when checking betting lines' plus explicit mode selection ('Pass game_id for one game... Or pass season...') gives the agent clear invocation conditions. There is no when-not guidance and no routing to the betting-adjacent siblings in the catalog, so the agent must infer the boundary itself.

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.