PuckAPI

Standings

get_standings

Read-onlyIdempotent

Use when checking where teams rank in their division or conference. Returns points, wins, losses, OT losses, point%, goal differential, goals for/against per game, and 5v5 possession: Corsi%, Fenwick% and expected goals for and against. The possession columns are 5v5 only, so they will not match a goalie's expected goals against, which covers every strength. Defaults to the most recent season with standings. Costs 2 credits.

Input Schema

Name	Required	Description
`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 current season.
`division`	No	Filter by division (e.g. Atlantic, Metropolitan, Central, Pacific)
`conference`	No	Filter by conference

Output Schema

Name	Required	Description	Default
`count`	Yes
`standings`	Yes
`snapshot_date`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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 a safe, idempotent read, so the lower bar applies, and the description clears it: it discloses the 2-credit cost, the default-season behavior, and a genuine analytical caveat that 5v5 possession columns will not match a goalie's all-situations expected goals. That caveat prevents a real misinterpretation of the data.

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 usage condition is front-loaded, followed by the returned metrics and then the caveat and cost. The metric enumeration is dense but each item is informative; nothing is redundant.

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 the description needn't document return structure, and it covers usage context, defaults, cost, and a data-interpretation caveat. What's missing is only a sibling comparison, which is a modest gap given 21 tools in the family.

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%, with enums documented for league and conference, so the schema carries the load. The description only adds the default-season behavior ('most recent season with standings'), which is a slight refinement of the schema's 'Defaults to current season' rather than new parameter guidance.

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 states a specific resource and the question it answers: team rankings within a division or conference. It enumerates the returned metrics, so the agent knows precisely what data it gets. It stops short of naming how it differs from sibling tools like get_team_stats, which is likely to be the main ambiguity.

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 where teams rank in their division or conference' gives a clear triggering context and implies the league/division/conference scoping via the schema. There is no explicit 'not for X, use Y instead' guidance against the many sibling stats tools.

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.