PuckAPI

Head to head

get_head_to_head

Read-onlyIdempotent

Use when comparing two teams' history. Returns recent matchups with win/loss record. Can filter by season or get all-time. Costs 10 credits.

Input Schema

Name	Required	Description
`limit`	No	Max games to return (default 20)
`team1`	Yes	First team abbreviation (e.g. BUF)
`team2`	Yes	Second team abbreviation (e.g. TOR)
`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. Omit for all-time.

Output Schema

Name	Required	Description	Default
`games`	Yes
`team1`	Yes
`team2`	Yes
`record`	Yes
`total_games`	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.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive semantics, so the bar is lower. The description still adds genuinely new behavioral context: it discloses a cost of 10 credits and summarizes the return shape (recent matchups with win/loss record), neither of which appears in the annotations.

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, front-loaded sentences — usage trigger first, then return content, then filtering mode, then cost. The telegraphic phrasing wastes nothing, though it borders on terse rather than explanatory.

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 needn't be detailed, and annotations carry the safety profile. With cost, scope, filtering modes and the two required teams covered, an agent has enough to call it correctly; only cross-tool routing guidance 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%, including team abbreviations, league enum, limit default and the season format, so the baseline is 3. The description's 'filter by season or get all-time' corroborates the season parameter's omit-for-all-time behavior but adds no format or edge-case detail beyond the schema.

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 — comparing two teams' history and returning recent matchups with a win/loss record — which is distinct from sibling list tools like get_games or get_team_stats. It does not explicitly name those siblings as alternatives, but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use when comparing two teams' history' gives a clear trigger condition, and 'Can filter by season or get all-time' frames the two modes of use. However, it never names an alternative tool (e.g. get_games or get_team_stats) or states when this tool is the wrong choice, so routing is left partly to inference.

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.