Skip to main content
Glama
nhl-stats-mcp

nhl-stats-mcp

by Bnocz

NHL league leaders

get_league_leaders
Read-only

Retrieve the current NHL season's league leaders by stat category, covering skater stats like points, goals, assists and goalie stats like wins, save percentage and shutouts.

Instructions

Get the current season's NHL leaders in a stat category. Skater categories: points (Points), goals (Goals), assists (Assists), plusMinus (Plus/minus), goalsPp (Power-play goals), goalsSh (Shorthanded goals), penaltyMins (Penalty minutes), toi (Time on ice per game), faceoffLeaders (Faceoff win %). Goalie categories: wins (Wins), savePctg (Save %), goalsAgainstAverage (Goals-against average), shutouts (Shutouts).

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_league_leaders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNopoints

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one real behavioral constraint beyond that: results are scoped to the current season only, so historical queries are out. It says nothing about how results are ordered, how many are returned, or what a response looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and scope, then a compact enumeration. The parenthetical glosses on category names each earn their place; there is no filler, though the list form makes it dense rather than scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 with no output schema, the definition covers the substantive parameter well and discloses the current-season scope. The unexplained limit parameter leaves genuine ambiguity about result-set size that matters precisely because no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage the description must carry the load, and it does fully for category, glossing non-obvious enum values like 'toi (Time on ice per game)', 'goalsPp (Power-play goals)', and 'faceoffLeaders (Faceoff win %)'. The limit parameter is never mentioned, so the default of 10 and the maximum of 25 are only discoverable from the schema.

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 the current season's NHL leaders in a stat category') and enumerates every valid stat category, split into skater and goalie groups. That enumeration implicitly separates it from player-level tools like get_player_stats, though it never names an alternative to route the agent away from.

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 category list implies when this tool fits (asking 'who leads the league in X'), and the skater/goalie split tells the agent which group a category belongs to. There is no explicit when-to-use vs. when-not guidance and no routing between this tool and get_player_stats or get_standings.

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