Skip to main content
Glama
nhl-stats-mcp

nhl-stats-mcp

by Bnocz

Search NHL players

search_players
Read-only

Find NHL players, current or retired, by full or partial name to resolve ambiguous names and retrieve player IDs, positions, and teams before requesting stats.

Instructions

Find NHL players (current and retired) by name. Returns player ids, positions and teams. Use this when a name is ambiguous before calling get_player_stats.

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": {
      "name": "<name>"
    },
    "name": "search_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull or partial player name
active_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description goes beyond that by disclosing that retired players are included by default and by naming the returned fields, which is real added context. It stops short of saying whether multiple matches are returned or whether there is a result cap, which is the remaining gap.

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 purpose, then return contents, then the routing instruction. Nothing is padded and no sentence merely restates the tool name.

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?

This is a simple two-parameter read tool with no output schema, and the description covers purpose, return contents, and when to use it, which is enough to call it correctly. The only missing piece an agent might want is the meaning of active_only and whether ambiguous names yield multiple rows.

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 only 50%: 'name' is documented in the schema, but 'active_only' has no description there. The phrase 'current and retired' hints that an active filter exists, yet the description never states that active_only=true restricts results to active players. Partial compensation, so the baseline 3 is right.

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?

States a specific verb and resource ('Find NHL players') plus the scope ('current and retired') and even the return payload ('player ids, positions and teams'). That combination clearly separates it from siblings like get_player_stats or get_team_roster, which are lookup/stat tools rather than name search.

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

Usage Guidelines5/5

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

Explicitly says when to reach for it ('when a name is ambiguous') and names the follow-up sibling ('before calling get_player_stats'), so the agent knows both the trigger condition and the sequencing. There is no ambiguity about which tool resolves a player name versus which one fetches stats.

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