Nhl

Get Scores

get_scores

Read-onlyIdempotent

Get today's NHL game scores and status (live, final, or scheduled). Returns teams, scores, shots on goal, and current period.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

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

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": {
+    "date": {
+      "description": "Current date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "games": {
+      "items": {
+        "properties": {
+          "away_score": {
+            "description": "Away team score",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "away_sog": {
+            "description": "Away team shots on goal",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "away_team": {
+            "description": "Away team name or abbreviation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "home_score": {
+            "description": "Home team score",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "home_sog": {
+            "description": "Home team shots on goal",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "home_team": {
+            "description": "Home team name or abbreviation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Game ID",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "period": {
+            "description": "Current period",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "start_time_utc": {
+            "description": "Start time in UTC",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "state": {
+            "description": "Game state (live, final, scheduled)",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_games": {
+      "description": "Total number of games",
+      "type": "number"
+    }
+  },
+  "required": [
+    "date",
+    "total_games",
+    "games"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 13, 2026

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

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "date": {
-      "description": "Current date",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "games": {
-      "items": {
-        "properties": {
-          "away_score": {
-            "description": "Away team score",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "away_sog": {
-            "description": "Away team shots on goal",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "away_team": {
-            "description": "Away team name or abbreviation",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "home_score": {
-            "description": "Home team score",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "home_sog": {
-            "description": "Home team shots on goal",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "home_team": {
-            "description": "Home team name or abbreviation",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "id": {
-            "description": "Game ID",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "period": {
-            "description": "Current period",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "start_time_utc": {
-            "description": "Start time in UTC",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "state": {
-            "description": "Game state (live, final, scheduled)",
-            "type": [
-              "string",
-              "null"
-            ]
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total_games": {
-      "description": "Total number of games",
-      "type": "number"
-    }
-  },
-  "required": [
-    "date",
-    "total_games",
-    "games"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "date": {
+      "description": "Current date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "games": {
+      "items": {
+        "properties": {
+          "away_score": {
+            "description": "Away team score",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "away_sog": {
+            "description": "Away team shots on goal",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "away_team": {
+            "description": "Away team name or abbreviation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "home_score": {
+            "description": "Home team score",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "home_sog": {
+            "description": "Home team shots on goal",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "home_team": {
+            "description": "Home team name or abbreviation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Game ID",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "period": {
+            "description": "Current period",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "start_time_utc": {
+            "description": "Start time in UTC",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "state": {
+            "description": "Game state (live, final, scheduled)",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_games": {
+      "description": "Total number of games",
+      "type": "number"
+    }
+  },
+  "required": [
+    "date",
+    "total_games",
+    "games"
+  ],
+  "type": "object"
+}

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

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive. The description adds value by specifying return fields (teams, scores, shots on goal, period), which is not covered by annotations. It does not contradict 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 sentence that efficiently communicates purpose and return contents. It is front-loaded with the key action ('Get today's NHL game scores and status'). No wasted words.

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 zero parameters, high schema coverage, existing output schema, and thorough annotations, the description fully covers what the tool does and returns. No missing context for selection or 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?

No parameters exist, so baseline is 4. The description does not need to add parameter info, and the schema coverage is 100%.

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 it retrieves today's NHL game scores and status, specifying exact return contents (teams, scores, shots on goal, current period). It distinguishes from sibling tools like get_schedule or get_standings by focusing on scores and live status.

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 use for today's games but does not explicitly contrast with siblings (e.g., get_schedule for future dates, get_standings for standings). No exclusionary or alternative guidance is provided.

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 Scores

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources