PuckAPI

Skater season stats

get_skater_season_stats

Read-onlyIdempotent

Use when ranking skaters or comparing scoring. Returns a leaderboard sorted by points, goals, assists, plus/minus, or shots, with a games-played filter. Includes power play and shorthanded production, shooting%, faceoff%, and average time on ice. Seasons from 2010-11 on. Costs 5 credits.

Input Schema

Name	Required	Description
`team`	No	Filter by team abbreviation
`limit`	No	Max results (default 20)
`league`	No	League. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl, ahl, ushl.
`season`	No	Season ID, 8-digit (e.g. 20242025 for 2024-25). 2024-25 and 2024-2025 also accepted. Defaults to the most recent season with stats, which is the current season once it is under way and the previous one before that. The season actually used is echoed in filters.season.
`sort_by`	No	Sort metric (default points)
`min_games`	No	Minimum games played (default 10; early in a season, half the most games anyone has played so far)

Output Schema

Name	Required	Description	Default
`count`	Yes
`filters`	Yes
`skaters`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / min_games / description

Previous value: -"Minimum games played (default 10)"New value: +"Minimum games played (default 10; early in a season, half the most games anyone has played so far)"

Changed2 schema fields changedOct 8, 2026

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

Changed2 schema fields changedOct 8, 2026

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

Changed1 schema field changedOct 5, 2026

addedInput schema / properties / league

Added value: +{
+  "description": "League. Defaults to nhl. One of: nhl, pwhl.",
+  "enum": [
+    "nhl",
+    "pwhl"
+  ],
+  "type": "string"
+}

First observedSep 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds value the annotations cannot: a 5-credit cost and the 2010-11 season floor, both of which affect whether an agent should call this at all.

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?

Four short sentences, each carrying a distinct fact (trigger, output shape, contents, constraints, cost), with the use case front-loaded. Dense and free of filler, though the mid-sentence metric list is slightly list-like.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 values need no explanation, and the description still summarizes what is included (power play, shorthanded, shooting%, faceoff%, TOI). Combined with the cost and season-range notes, an agent has enough to call it correctly; only explicit sibling routing is absent.

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%, so all six parameters (team, limit, league, season, sort_by, min_games) are already documented with defaults and constraints. The description only echoes the sort metrics and games-played filter, adding nothing beyond the schema except the historical season range.

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 specific verb and resource ('Returns a leaderboard sorted by points, goals, assists...'), making it distinguishable from get_player_stats and get_goalie_stats by its ranking/leaderboard framing. It stops short of explicitly naming the sibling it is not, which keeps it below a 5.

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 ranking skaters or comparing scoring' gives a clear positive trigger condition, which is unusually direct. It does not state when NOT to use it or name the alternative to pick instead for single-player lookups.

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.