Skip to main content
Glama

PuckAPI

by com.puckapi.mcp
OverviewDiscussionsAdmin
This connector has been deprecated

Moved to a server instead of a connector

get_player_game_log

Read-only

Use when you need a player's game-by-game stat lines for a season, not a season total. For skaters: date, opponent, home/away, goals, assists, points, shots, PIM and power-play points for each game. For goalies: date, opponent, home/away, decision, shots against, saves, goals against and save% for each game. Built from play-by-play, so time on ice and plus/minus are not available and come back null; goalie time on ice is available only for games the goalie started. Requires player ID from search_players. Costs 5 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax games to return (default 100)
leagueNoLeague. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl, ahl, ushl.
offsetNoPagination offset
seasonNoSeason ID, 8-digit (e.g. 20242025 for 2024-25). 2024-25 and 2024-2025 also accepted. Defaults to the most recent season with stats for this player, which is the current season once it is under way and the previous one before that. The season actually used is echoed back in the response.
game_typeNoWhich games to include: regular, playoff, preseason, or all. Defaults to regular, matching every other stats tool.
player_idYesNHL player ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
countYes
gamesYes
playerYes
seasonYes
game_typeYes
next_offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / league / description
      Previous value: -"League. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl."New value: +"League. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl, ahl, ushl."
    • changedInput schema / properties / league / enum
      Previous value: -[
-  "nhl",
-  "pwhl",
-  "ohl",
-  "whl",
-  "qmjhl",
-  "echl"
-]New value: +[
+  "nhl",
+  "pwhl",
+  "ohl",
+  "whl",
+  "qmjhl",
+  "echl",
+  "ahl",
+  "ushl"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / league / description
      Previous value: -"League. Defaults to nhl. One of: nhl, pwhl."New value: +"League. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl."
    • changedInput schema / properties / league / enum
      Previous value: -[
-  "nhl",
-  "pwhl"
-]New value: +[
+  "nhl",
+  "pwhl",
+  "ohl",
+  "whl",
+  "qmjhl",
+  "echl"
+]
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight and does: it discloses the data provenance ('built from play-by-play') and the resulting gaps ('time on ice and plus/minus ... come back null; goalie time on ice is available only for games the goalie started'). It also notes the season actually used is echoed in the response, which sets expectations about return content and cost.

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 the use condition and the key exclusion, then the field lists, then caveats and prerequisites. The two stat enumerations are long but earn their place by letting an agent verify the tool returns the metric it needs. Slightly dense, but no filler sentences.

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?

An output schema exists, so return-shape explanation is not owed, yet the description still preempts the most likely support question (missing TOI/plus-minus) that an output schema alone would not explain. Combined with prerequisites, cost, and the season-echo behavior, nothing needed to call this correctly is missing.

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 description coverage is already 100%, with league, game_type, season, limit and offset all documented in-schema including defaults and formats. The description adds no syntax or constraint detail beyond that, so the baseline 3 applies; its value is in describing output content rather than parameter behavior.

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?

Opens with a specific trigger and resource: 'a player's game-by-game stat lines for a season, not a season total.' That negative clause immediately separates it from the season-total siblings (get_player_stats, get_skater_season_stats). It then enumerates the exact stat columns returned for skaters and goalies, so the agent knows precisely what this tool produces.

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?

States the when ('game-by-game stat lines for a season'), the when-not ('not a season total'), and the prerequisite ('Requires player ID from search_players'), which chains it to the correct sibling for ID lookup. It also surfaces the cost ('Costs 5 credits'), which is decision-relevant for an agent weighing alternatives.

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

All PuckAPI toolsInspect
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