Skip to main content
Glama

Nhl

by io.github.pipeworx-io

Get Player

get_player
Read-onlyIdempotent

Get an NHL player's profile and current season stats by player ID. Returns bio, position, team, and season statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playerIdYesNHL player ID (e.g., 8478402 for Connor McDavid)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoPlayer full name
teamNoCurrent team name
numberNoJersey number
headshotNoHeadshot image URL
positionNoPlayer position
height_inNoHeight in inches
player_idNoPlayer ID
birth_cityNoBirth city
birth_dateNoBirth date
weight_lbsNoWeight in pounds
team_abbrevNoCurrent team abbreviation
birth_countryNoBirth country
current_season_statsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "playerId": 8478402
+  },
+  {
+    "playerId": 8477933
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "birth_city": {
+      "description": "Birth city",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "birth_country": {
+      "description": "Birth country",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "birth_date": {
+      "description": "Birth date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "current_season_stats": {
+      "properties": {
+        "assists": {
+          "description": "Assists",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "games_played": {
+          "description": "Games played",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "goals": {
+          "description": "Goals scored",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "pim": {
+          "description": "Penalties in minutes",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "plus_minus": {
+          "description": "Plus/minus rating",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "points": {
+          "description": "Total points",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "season": {
+          "description": "Season year",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "headshot": {
+      "description": "Headshot image URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "height_in": {
+      "description": "Height in inches",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Player full name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "number": {
+      "description": "Jersey number",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "player_id": {
+      "description": "Player ID",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "position": {
+      "description": "Player position",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "team": {
+      "description": "Current team name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "team_abbrev": {
+      "description": "Current team abbreviation",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "weight_lbs": {
+      "description": "Weight in pounds",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "_apiKey": "your-nba-api-key",
-    "id": 114
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "college": {
-      "description": "College attended",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "country": {
-      "description": "Country of origin",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "draft_number": {
-      "description": "Draft pick number",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "draft_round": {
-      "description": "Draft round",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "draft_year": {
-      "description": "Year drafted",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "height": {
-      "description": "Player height",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "id": {
-      "description": "Player ID",
-      "type": "number"
-    },
-    "jersey_number": {
-      "description": "Jersey number",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "name": {
-      "description": "Full name (first + last)",
-      "type": "string"
-    },
-    "position": {
-      "description": "Player position",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "team": {
-      "description": "Current team information",
-      "properties": {
-        "abbreviation": {
-          "description": "Team abbreviation",
-          "type": "string"
-        },
-        "city": {
-          "description": "Team city",
-          "type": "string"
-        },
-        "conference": {
-          "description": "Conference (East/West)",
-          "type": "string"
-        },
-        "division": {
-          "description": "Division name",
-          "type": "string"
-        },
-        "full_name": {
-          "description": "Full team name",
-          "type": "string"
-        },
-        "id": {
-          "description": "Team ID",
-          "type": "number"
-        },
-        "name": {
-          "description": "Team name",
-          "type": "string"
-        }
-      },
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "weight": {
-      "description": "Player weight",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "id",
-    "name",
-    "position",
-    "height",
-    "weight",
-    "jersey_number",
-    "college",
-    "country",
-    "draft_year",
-    "draft_round",
-    "draft_number",
-    "team"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "college": {
+      "description": "College attended",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "country": {
+      "description": "Country of origin",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "draft_number": {
+      "description": "Draft pick number",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "draft_round": {
+      "description": "Draft round",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "draft_year": {
+      "description": "Year drafted",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "height": {
+      "description": "Player height",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Player ID",
+      "type": "number"
+    },
+    "jersey_number": {
+      "description": "Jersey number",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Full name (first + last)",
+      "type": "string"
+    },
+    "position": {
+      "description": "Player position",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "team": {
+      "description": "Current team information",
+      "properties": {
+        "abbreviation": {
+          "description": "Team abbreviation",
+          "type": "string"
+        },
+        "city": {
+          "description": "Team city",
+          "type": "string"
+        },
+        "conference": {
+          "description": "Conference (East/West)",
+          "type": "string"
+        },
+        "division": {
+          "description": "Division name",
+          "type": "string"
+        },
+        "full_name": {
+          "description": "Full team name",
+          "type": "string"
+        },
+        "id": {
+          "description": "Team ID",
+          "type": "number"
+        },
+        "name": {
+          "description": "Team name",
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "weight": {
+      "description": "Player weight",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "position",
+    "height",
+    "weight",
+    "jersey_number",
+    "college",
+    "country",
+    "draft_year",
+    "draft_round",
+    "draft_number",
+    "team"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-nba-api-key",
+    "id": 114
+  }
+]
  5. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. The description adds that it returns specific data fields, but does not disclose any additional behavioral traits such as rate limits, caching, or error behavior.

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 a single sentence that front-loads the core purpose and then specifies return content. Every word is informative; there is no fluff or redundancy.

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?

Given the simple single-parameter tool with an output schema (has output schema: true) and safety annotations, the description covers all necessary aspects: what it does, how to call it (by ID), and what to expect in return. No gaps are apparent.

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?

The sole parameter playerId is documented in both the tool description and schema (100% coverage). The schema provides an example and explanation, which adds meaning beyond the parameter name. The description reinforces the parameter's purpose without redundancy.

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 uses a specific verb 'Get', identifies the resource 'NHL player's profile and current season stats', and lists key output components (bio, position, team, season statistics). It clearly distinguishes from sibling tools like get_schedule or get_scores.

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?

The description clearly states it fetches player data by ID, but does not explicitly mention when to use this tool over alternatives like entity_profile, nor does it provide exclusions or prerequisites. The usage context is implied but not explicit.

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

All Nhl toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

The set contains multiple near-overlapping query tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools) and a cluster of prediction-market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) with fuzzy boundaries. ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, making misselection likely.

Naming Consistency2/5

Naming is mixed across clusters: get_* for NHL tools, ask_pipeworx* for queries, polymarket_* for prediction markets, bare verbs (remember, recall, forget), and noun_verb phrases (entity_profile, recent_changes, scan_dependency). Each cluster is internally consistent, but there is no unifying pattern across the server.

Tool Count1/5

35 tools on a server named 'Nhl' is an extreme mismatch: only 4 tools actually relate to NHL data, while the other 31 are a general-purpose Pipeworx data/research/prediction-market platform. The set is not well-scoped for its apparent purpose, and even as a general data server it feels like a grab bag of unrelated capabilities.

Completeness2/5

For the NHL domain the surface is thin: player, schedule, scores, and standings, but no team info, roster lookup, player search by name, or game/play-by-play details. The Pipeworx side is more complete but fills the server with functionality unrelated to the NHL branding, so the overall surface is fragmented and leaves obvious domain gaps.

Resources