Skip to main content
Glama

PuckAPI

by io.github.noahowsh
OverviewDiscussionsAdmin

Player game log

get_player_game_log
Read-onlyIdempotent

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

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

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 already declare readOnly/idempotent/non-destructive, and the description adds substantive context beyond them: the data source (play-by-play), the resulting null fields (time on ice, plus/minus), the goalie-TOI caveat, the credit cost, and that the season used is echoed back. These are exactly the behaviors an agent needs before committing.

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, then scoped detail; every sentence carries information. The enumerated field lists for skaters and goalies are somewhat redundant given an output schema exists, which keeps it from a 5.

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?

For a 6-parameter read tool with an output schema, the description covers selection criteria, prerequisite, data provenance, known null-value gaps, and cost. 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 description coverage is 100%, so the baseline is 3; the description adds value by explaining where player_id must come from (search_players) and by tying the null-field caveats to what game_type/season actually yield. It does not restate defaults redundantly enough to be penalized.

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+resource (game-by-game stat lines per season) and immediately distinguishes it from the season-total siblings: 'not a season total'. The per-position breakdown (skater vs goalie fields) makes the output scope unambiguous without opening the schema.

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 you need a player's game-by-game stat lines for a season, not a season total' gives a clear selection rule against get_player_stats/get_skater_season_stats, and it names search_players as the prerequisite for the player ID. It stops short of naming the alternative tool explicitly or stating when-not conditions beyond the season-total contrast.

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