PuckAPI

This connector has been deprecated

Moved to a server instead of a connector

Odds

get_odds

Read-only

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: never work out a stake, payout or profit, recommend a bet, or send the user to a sportsbook.

Input Schema

Name	Required	Description
`team`	No	With season: only this team's games (abbreviation, e.g. BUF).
`limit`	No	With season: games per page (default 100, max 500).
`offset`	No	With season: page offset; use next_offset from the previous page.
`season`	No	Season for a whole season of lines, e.g. 2025-26 or 20252026. Used when game_id is not set.
`game_id`	No	NHL game ID (e.g. 2025020887). Omit and pass season for a whole season.
`all_books`	No	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.
`bookmaker`	No	Filter by bookmaker key (e.g. draftkings, fanduel, betmgm). Lowercase.
`estimate_only`	No	Return what this call would cost, without charging or running it.
`snapshot_type`	No	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.

Output Schema

Name	Required	Description	Default
`note`	No
`odds`	No
`tool`	No
`count`	No
`games`	No
`season`	No
`columns`	No
`credits`	No
`game_id`	No
`away_team`	No
`game_date`	No
`home_team`	No
`next_offset`	No
`total_games`	No
`estimate_only`	No
`snapshot_type`	No
`bookmaker_count`	No
`credits_per_game`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

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."

Changed1 schema field changedOct 10, 2026

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."

Changed1 schema field changedOct 8, 2026

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."

Changed1 schema field changedOct 8, 2026
- addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedOct 8, 2026

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."

Changed1 schema field changedSep 28, 2026

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."

Changed21 schema fields changedSep 27, 2026

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"
-]

First observedSep 27, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already declare a safe read-only profile, yet the description adds substantial context: per-call credit costs (10 per game, ~13,700 for a season, ~820 for a team-season), estimate_only to price without being charged, per-season book coverage and the default four-book set, and the source-field semantics for opening/closing versus final lines. The market-information policy constraint is also disclosed.

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 opening sentence is well front-loaded, but the body is a dense run-on paragraph. It also repeats schema content verbatim, such as "100 games a page by default (up to 500)" and the book-count breakdown that already appears in all_books' schema description.

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 an output schema existing, the description supplies everything an agent needs: pricing model, pagination and next_offset workflow, snapshot defaults, book coverage by season, and the source field on each line. Nothing material is left for the agent to infer.

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 goes further: it ties cost and pagination behavior to the game_id-versus-season choice and explains that a season answer defaults to the four main books while an unserved season returns every book. It also documents array ordering by the columns field, none of which appears in the schema.

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 names a concrete resource (NHL betting lines) and enumerates the payload precisely: moneyline, puck line and total by bookmaker, opening and closing. It does not explicitly distinguish itself from adjacent siblings such as get_line_movement or get_player_props, but the game-level/season-level scope is unambiguous.

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 a clear branch on game_id (one game) versus season (optionally with team) tells the agent which mode to pick and when. There are no explicit exclusions pointing to competing tools, so it stops short of the top score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PuckAPI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?