Nhl

Get Schedule

get_schedule

Read-onlyIdempotent

Get the current NHL weekly schedule. Returns upcoming and recent games with teams, dates, times, and venues.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`games`	Yes
`total_games`	Yes	Total number of games in schedule
`current_date`	Yes	Current date

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "current_date": {
+      "description": "Current date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "games": {
+      "items": {
+        "properties": {
+          "away_team": {
+            "description": "Away team name or abbreviation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "date": {
+            "description": "Game date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "home_team": {
+            "description": "Home team name or abbreviation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Game ID",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "start_time_utc": {
+            "description": "Start time in UTC",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "state": {
+            "description": "Game state",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "venue": {
+            "description": "Venue name",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_games": {
+      "description": "Total number of games in schedule",
+      "type": "number"
+    }
+  },
+  "required": [
+    "current_date",
+    "total_games",
+    "games"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 12, 2026

removedInput schema / examples
```
Removed value: -[
-  {}
-]
```

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "current_date": {
-      "description": "Current date",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "games": {
-      "items": {
-        "properties": {
-          "away_team": {
-            "description": "Away team name or abbreviation",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "date": {
-            "description": "Game date",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "home_team": {
-            "description": "Home team name or abbreviation",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "id": {
-            "description": "Game ID",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "start_time_utc": {
-            "description": "Start time in UTC",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "state": {
-            "description": "Game state",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "venue": {
-            "description": "Venue name",
-            "type": [
-              "string",
-              "null"
-            ]
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total_games": {
-      "description": "Total number of games in schedule",
-      "type": "number"
-    }
-  },
-  "required": [
-    "current_date",
-    "total_games",
-    "games"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "current_date": {
+      "description": "Current date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "games": {
+      "items": {
+        "properties": {
+          "away_team": {
+            "description": "Away team name or abbreviation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "date": {
+            "description": "Game date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "home_team": {
+            "description": "Home team name or abbreviation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Game ID",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "start_time_utc": {
+            "description": "Start time in UTC",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "state": {
+            "description": "Game state",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "venue": {
+            "description": "Venue name",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_games": {
+      "description": "Total number of games in schedule",
+      "type": "number"
+    }
+  },
+  "required": [
+    "current_date",
+    "total_games",
+    "games"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {}
+]
```
First observedApr 22, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the tool's safety and behavior are covered. The description adds that it returns 'upcoming and recent games with teams, dates, times, and venues', which provides useful context but does not conflict with annotations.

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, clear sentence with no unnecessary words. It is front-loaded with the action and resource, then specifies the return content. Every word earns its place.

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 no parameters, rich annotations covering behavioral traits, and an output schema, the description is complete. It tells exactly what the tool returns, leaving no ambiguity for a simple parameterless tool.

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 input schema has no parameters, so schema_description_coverage is 100%. The description adds meaning by listing the types of data returned (teams, dates, times, venues), which helps the agent understand the output, even though an output schema exists. Baseline for 0 params is 4.

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 clearly states the tool gets the 'current NHL weekly schedule' and specifies it returns 'upcoming and recent games with teams, dates, times, and venues'. The verb 'get' and resource 'NHL weekly schedule' are specific, and it easily distinguishes from siblings like get_scores, get_standings, and get_player.

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 implies usage when schedule information is needed, but does not explicitly state when to use or not use this tool compared to alternatives. There is no mention of exclusions or conditions, though the context is clear.

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

All Nhl tools Inspect

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.

Get Schedule

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources