Nhl

Get Standings

get_standings

Read-onlyIdempotent

Check current NHL standings. Returns wins, losses, OT losses, points, goals for/against, and streak info for all teams.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes	Total number of teams in standings
`standings`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "standings": {
+      "items": {
+        "properties": {
+          "abbrev": {
+            "description": "Team abbreviation",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "conference": {
+            "description": "Conference name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "division": {
+            "description": "Division name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "games_played": {
+            "description": "Games played",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "goals_against": {
+            "description": "Goals allowed",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "goals_for": {
+            "description": "Goals scored",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "losses": {
+            "description": "Losses",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Team name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ot_losses": {
+            "description": "Overtime losses",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "points": {
+            "description": "Standing points",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "streak": {
+            "description": "Current win/loss streak (e.g., W5, L2)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "wins": {
+            "description": "Wins",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of teams in standings",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "standings"
+  ],
+  "type": "object"
+}

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

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds value by specifying the exact return fields (wins, losses, OT losses, points, goals for/against, streak info), which aids in understanding the behavior beyond the 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?

Two sentences, front-loaded with the main purpose, no extraneous words. Every word earns its place.

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 no parameters and an existing output schema (as indicated), the description provides sufficient context about the return data. It covers the key fields, making it complete for a simple listing 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 tool has zero parameters, so the baseline is 4. The description does not need to add parameter information, and it correctly leaves the schema handle the (empty) parameter definitions.

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 uses the verb 'Check' and the resource 'current NHL standings', listing the specific data fields returned. It distinguishes itself from sibling tools like get_player, get_schedule, and 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 states what the tool does but provides no explicit guidance on when to use it versus alternatives, nor any conditions or exclusions. The purpose is clear, but usage context is minimal.

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.