Skip to main content
Glama
nhl-stats-mcp

nhl-stats-mcp

by Bnocz

NHL team roster

get_team_roster
Read-only

Retrieve a team's current NHL roster—forwards, defensemen, and goalies—including jersey numbers, positions, and player IDs by team abbreviation or name.

Instructions

Get a team's current roster: forwards, defensemen and goalies with numbers, positions and player ids.

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

Input Schema

NameRequiredDescriptionDefault
teamYesTeam abbreviation or name, e.g. "TOR", "Leafs", "Toronto Maple Leafs", "Habs"

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, covering the safety profile. With no output schema, the description usefully enumerates the returned fields, but it says nothing about behavior for ambiguous or invalid team names, data freshness/season scope, or response shape beyond the category list.

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?

One sentence, front-loaded with the action and resource, followed by the content returned. No filler or redundancy.

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 one-parameter read tool with annotations covering safety/open-world and a fully documented parameter, the description covers purpose and return contents adequately. It could be more complete by noting season/date scope of 'current' and how fuzzy team-name matches resolve.

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 includes concrete examples ('TOR', 'Leafs', 'Toronto Maple Leafs'), so the single parameter is fully documented in the schema. The description adds no meaning beyond that, which is the baseline for high-coverage schemas.

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 gives a specific verb plus resource ('Get a team's current roster') and enumerates the returned content (forwards, defensemen, goalies with numbers, positions, player ids), so the agent can distinguish it from schedule/standings/stat tools even without named exclusions.

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 word 'current' implies the roster-composition use case, but there is no explicit when-to-use statement and no mention of the natural alternatives (get_player_stats for performance data, search_players for finding a player). 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.