Skip to main content
Glama
nhl-stats-mcp

nhl-stats-mcp

by Bnocz

NHL player stats

get_player_stats
Read-only

Retrieve an NHL player's profile, current-season and career regular-season stats, and last five games by name or numeric ID; supports skaters and goalies.

Instructions

Get a player's profile, current-season and career regular-season stats, and their last 5 games. Accepts a player name (e.g. "McDavid") or a numeric NHL player id. Works for skaters and goalies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "player": "<player>"
    },
    "name": "get_player_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerYesPlayer name or 7-digit NHL player id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 externally; the description adds useful substance by listing exactly which stat blocks are returned (profile, current season, career regular season, last 5 games) and that both skaters and goalies are supported. It does not disclose what happens on an ambiguous or unmatched name, whether name resolution picks a single player, or any caching/rate behavior for an open-world lookup.

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?

Three short sentences, front-loaded with what is returned, then accepted input forms, then the skater/goalie scope note. No filler or redundant phrasing.

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?

With no output schema, the description correctly compensates by enumerating the returned sections, so an agent knows what it will get back. Remaining gaps are minor for a read-only lookup: no note on ambiguous-name resolution or not-found behavior.

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?

Schema coverage is 100% with a single documented parameter ('Player name or 7-digit NHL player id'), so the schema already carries the semantics. The description's mention of name-or-id and the 'McDavid' example largely restates the schema, though the example usefully illustrates the expected name format; baseline 3 applies.

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?

Names a specific verb and resource ('Get a player's profile, current-season and career regular-season stats, and their last 5 games') and enumerates the return contents, which is more than a restatement of the name. It distinguishes itself loosely from search_players by accepting a name directly, but never names that sibling as the lookup alternative.

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?

Gives clear input guidance ('Accepts a player name (e.g. "McDavid") or a numeric NHL player id') and scope ('Works for skaters and goalies'), which implies when to use it. It offers no explicit when-not conditions or comparison to siblings like search_players or get_league_leaders, so selection guidance is only implied.

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