Skip to main content
Glama
nhl-stats-mcp

nhl-stats-mcp

by Bnocz

NHL standings

get_standings
Read-only

Retrieve NHL standings by league, conference, or division, including wins, losses, OT losses, points, goal differential, last 10, and streak for a given date or today.

Instructions

Get NHL standings (W-L-OTL, points, point %, goal differential, last 10, streak), grouped league-wide, by conference or by division.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Omit for today (US Eastern time).
groupNodivision

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful context by saying the standings can be grouped three ways and listing the stats returned, but says nothing about season scope, whether data is live or cached, or how ties are handled.

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?

A single front-loaded sentence with the verb, resource, returned fields and grouping options in that order. No filler, nothing repeated.

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?

For a simple two-parameter read tool with no output schema, the description carries the main missing piece — what the response contains — and covers the grouping parameter. Season or timeframe behavior is left implicit, which is a modest gap.

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?

Schema coverage is 50%: the `date` parameter is fully documented in the schema, but `group` only appears as an enum with a default and no description. The description compensates by explaining the three grouping modes (league-wide, conference, division), giving the enum meaning the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (get NHL standings) and enumerates the fields returned (W-L-OTL, points, point %, goal differential, last 10, streak), which separates it from siblings like get_scores or get_league_leaders. It stops short of explicitly contrasting with those siblings, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. The agent must infer that this is the tool for table-style standings rather than game results or stat leaderboards.

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