Skip to main content
Glama

PuckAPI

by com.puckapi.mcp
OverviewDiscussionsAdmin
This connector has been deprecated

Moved to a server instead of a connector

get_head_to_head

Read-only

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

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax games to return (default 20)
team1YesFirst team abbreviation (e.g. BUF)
team2YesSecond team abbreviation (e.g. TOR)
leagueNoLeague. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl, ahl, ushl.
seasonNoSeason ID, 8-digit (e.g. 20242025 for 2024-25). 2024-25 and 2024-2025 also accepted. Omit for all-time.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
gamesYes
team1Yes
team2Yes
recordYes
total_gamesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+]
  2. Changed2 schema fields changed
    • 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"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / league
      Added value: +{
+  "description": "League. Defaults to nhl. One of: nhl, pwhl.",
+  "enum": [
+    "nhl",
+    "pwhl"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds valuable behavioral context: the credit cost (10 credits) and the ability to filter or get all-time, which goes beyond annotations. However, it doesn't detail pagination or return format, but output schema exists.

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?

Three short sentences, front-loaded with usage, then output, then filtering and cost. Every sentence earns its place with zero waste.

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?

Given the tool complexity, annotations, and output schema, the description is nearly complete. It covers when to use, what it returns, filtering options, and cost. Only minor gap is absence of explicit alternatives, but overall sufficient.

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 the schema already fully documents all parameters including defaults and formatting. The description mentions filtering by season or all-time, which aligns with the schema's season parameter, but adds no new semantic detail. Baseline 3 is appropriate.

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?

States a specific verb (comparing) and resource (two teams' history), and clearly distinguishes from siblings like get_games or get_team_stats. The output focus on recent matchups with win/loss record is explicit.

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 'when to use' context: comparing two teams' history. It also distinguishes filtering by season vs all-time. Missing explicit when-not-to-use or alternative sibling names, but the context is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PuckAPI toolsInspect
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