Nhl

Nhl Get Player

nhl_get_player

Read-onlyIdempotent

Get an NHL player's profile and current season stats by player ID. Returns bio, position, team, and season statistics.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

Name	Required	Description	Default
`playerId`	Yes	NHL player ID (e.g., 8478402 for Connor McDavid)

Output Schema

Name	Required	Description
`name`	No	Player full name
`team`	No	Current team name
`number`	No	Jersey number
`headshot`	No	Headshot image URL
`position`	No	Player position
`height_in`	No	Height in inches
`player_id`	No	Player ID
`birth_city`	No	Birth city
`birth_date`	No	Birth date
`weight_lbs`	No	Weight in pounds
`team_abbrev`	No	Current team abbreviation
`birth_country`	No	Birth country
`current_season_stats`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

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, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds the shape of the payload at a high level (bio, position, team, season statistics), which is modest added value given an output schema already exists. No notes on failure behavior for invalid or retired player IDs.

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 short sentences, front-loaded with the core action and immediately followed by the return contents. Slight redundancy between 'current season stats' and 'season statistics', but no padding or tangents.

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 one fully documented parameter, rich annotations, and an output schema, the description covers what is needed to call the tool correctly. The only material gap is not explaining how an agent should source the numeric player ID when it only has a name.

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 description coverage is 100% and the single playerId parameter already carries an inline example (8478402 for Connor McDavid), so the schema does the heavy lifting. The description only restates the lookup key ('by player ID') without adding format rules, valid ranges, or resolution guidance, which is the expected baseline for a fully documented single parameter.

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?

The description states a specific verb and resource ('Get an NHL player's profile and current season stats') plus the lookup key ('by player ID'), so an agent knows exactly what it retrieves. It does not explicitly distinguish itself from siblings like nhl_get_scores or nhl_get_standings, though the player-versus-game/league scope is implied by the name and description.

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?

Usage is only implied: the phrase 'by player ID' signals that a valid player identifier is a prerequisite, which is useful context for invocation. There is no explicit when-to-use versus when-not guidance and no mention of how to obtain a player ID or what to do if the ID is unknown.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.