PuckAPI

This connector has been deprecated

Moved to a server instead of a connector

Plays

get_plays

Read-only

Use for play-by-play events: goals, shots, misses, blocks, faceoffs, hits, giveaways, takeaways, penalties, with rink coordinates, strength state (5v5, 5v4), zone, and the players involved. Filter by game, season, team, player (any role), event type, strength, zone, or period. Requires at least one of game_id, season or player_id. Paginate with offset. Costs 10 credits.

Input Schema

Name	Required	Description
`team`	No	Team abbreviation that owns the event (e.g. BUF)
`type`	No	Event type
`zone`	No	Zone: O offensive, N neutral, D defensive
`limit`	No	Max events (default 200)
`league`	No	League. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl, ahl, ushl.
`offset`	No	Pagination offset
`period`	No	Period number (4+ is overtime)
`season`	No	Season ID, 8-digit (e.g. 20242025).
`game_id`	No	NHL game ID (e.g. 2025020887)
`strength`	No	Skater strength from the event owner's view, e.g. 5v5, 5v4, 4v5
`player_id`	No	NHL player ID; matches the player in any role on the event
`shot_attempts_only`	No	Only goals, shots on goal, missed shots and blocked shots (Corsi events)

Output Schema

Name	Required	Description	Default
`count`	Yes
`plays`	Yes
`summary`	Yes
`next_offset`	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

A4.2/5.0

Behavior4/5

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

Annotations already establish read-only and non-destructive behavior. The description adds valuable operational details: a cross-parameter requirement (at least one of game_id, season, or player_id), pagination via offset, and a 10-credit cost. It does not cover auth or rate limits beyond cost.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five tight sentences, front-loaded with purpose, then filters, requirement, pagination, and cost. Every sentence carries actionable information; no waste.

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 12-parameter read-only tool with an output schema and full annotation coverage, the description supplies the essential calling constraints: required filter, pagination, cost, and event scope. Nothing critical is missing for correct invocation.

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 coverage is 100%, so baseline is 3. The description adds a critical cross-parameter constraint not expressed in the schema (at least one of game_id, season, or player_id) and maps filters to parameters. It does not add syntax or format details for individual parameters, but the constraint is meaningful.

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?

States a specific resource (play-by-play events) and enumerates event types with attributes like rink coordinates and strength state, giving a clear sense of what the tool returns. It does not explicitly differentiate itself from siblings such as get_shot_map or get_shifts, so 4 rather than 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?

Provides clear context 'Use for play-by-play events' and lists filterable dimensions, but offers no when-not guidance or named alternatives for related tools. Clear enough but lacks exclusion criteria.

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.

Resources

Need Help?