PuckAPI

Search players

search_players

Read-onlyIdempotent

Use when looking up a player by name. Searches 4,900+ players across every season since 2010-11. Returns active players by default; set active=false for retired/historical. Use the returned player ID with get_player_stats for full details. Costs 2 credits.

Input Schema

Name	Required	Description
`team`	No	Filter by team abbreviation
`limit`	No	Max results (default 10)
`query`	Yes	Player name to search for (partial match supported)
`active`	No	Filter by active status (default: true). Set false to search active plus retired/historical players.
`league`	No	League. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl, ahl, ushl.
`position`	No	Filter by position

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`players`	Yes
`included_inactive`	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.3/5.0

Behavior4/5

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

Annotations already declare this as a safe, read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond annotations: default active-only results, historical scope via active=false, and a concrete cost of 2 credits. It does not describe pagination or result-shape behavior, so it is not exhaustive.

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?

The description is four tight sentences with no wasted wording. The primary use case is front-loaded, followed by scope, default behavior, next-step routing, and cost.

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?

An output schema exists, so the description need not explain return values. Given the 100% schema coverage, clear annotations, and the description's coverage of use case, defaults, next tool, and cost, an agent has enough information to select and invoke this tool correctly.

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 are already documented in the schema. The description reinforces the important active-status default and clarifies that query is a name search, but it does not add syntax or meaning beyond what the schema already provides.

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 ('looking up a player by name') and adds scope ('4,900+ players across every season since 2010-11'). It also distinguishes this lookup tool from get_player_stats by explaining that the returned player ID should be used there for full details.

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?

It gives a clear usage context ('Use when looking up a player by name') and names the follow-up tool get_player_stats for full details. It also explains the default active-player behavior and how to include retired/historical players, though it does not explicitly state when not to use this tool.

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.