Skip to main content
Glama

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, power-play points, time on ice and plus/minus for each game. For goalies: date, opponent, home/away, decision, shots against, saves, goals against, save% and time on ice for each game. Time on ice and plus/minus are the official NHL boxscore figures, loaded with each game's shift chart (2010-11 on); a game not loaded yet shows null. Requires player ID from search_players. Costs 5 credits.

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": {
      "player_id": "<player_id>"
    },
    "name": "get_player_game_log"
  }
}

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.4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower, yet the description adds real operational context: TOI and plus/minus come from the official boxscore loaded with each game's shift chart (2010-11 onward), games not yet loaded return null, and the call costs 5 credits. Those are caveats an agent cannot infer from structured fields and they directly affect how results should be interpreted.

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?

The selection condition is front-loaded in the first sentence and the rest is dense, factual detail. The long field enumerations for skaters and goalies are partly redundant with the existing output schema, which costs some economy, but they aid fast scanning rather than padding.

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 filtered per-game log with six parameters and an output schema, the description covers selection criteria, prerequisites (player ID from search_players), data provenance and null semantics, and cost. Nothing material 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including detailed enum and season-format docs, so the schema carries parameter meaning. The description only loosely reinforces season scoping and never mentions league, game_type, limit or offset, so it adds little beyond the schema; baseline 3 applies.

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 states a specific verb and resource ('a player's game-by-game stat lines for a season') and immediately contrasts it with season totals, which separates it from get_player_stats / get_skater_season_stats / get_goalie_stats without opening their schemas. It even enumerates the exact stat fields returned for skaters versus goalies, so the agent knows precisely what it gets.

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 ... not a season total' gives an explicit selection condition and an explicit exclusion class, and 'Requires player ID from search_players' routes the agent to the prerequisite tool. It stops short of naming the specific alternative tool, so the agent must still map 'season total' to the right sibling 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.