Skip to main content
Glama
nhl-stats-mcp

nhl-stats-mcp

by Bnocz

NHL scores

get_scores
Read-only

Fetch NHL game scores for a specific date: live period and clock, final scores, or start times, with optional goal details including scorer, assists, and strength.

Instructions

Get NHL games for a date: live scores with period and clock, final scores, or start times for upcoming games. Set include_goals to list every goal with scorer, assists and strength.

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

Input Schema

NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Omit for today (US Eastern time).
include_goalsNoList each goal scored in started games

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 safety is covered. The description adds genuine behavioral context beyond that: the response shape varies by game state (live period/clock vs final vs scheduled start time), and include_goals changes the payload to per-goal detail with scorer, assists and strength. It does not mention rate limits or data freshness, but the state-dependent output disclosure is the substantive part.

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?

Two sentences with no filler. The core resource and date scope are front-loaded, and the second sentence is dedicated entirely to the one optional flag that changes output volume.

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 must convey return shape, and it does so by naming the three game states and what each yields. Nothing critical for a zero-required-parameter read tool is missing, though a note on the date default and timezone appears only in the schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema's terse 'List each goal scored in started games' by specifying what a listed goal contains (scorer, assists, strength), which meaningfully clarifies the flag's cost and payload impact.

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 names a specific verb and resource ('Get NHL games for a date') and enumerates the three result states an agent can expect: live with period/clock, final, or upcoming start times. It is clearly distinguishable from stat-oriented siblings like get_standings or get_player_stats, though it does not explicitly contrast itself with get_team_schedule, which also returns games.

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: an agent can infer 'use this to get scores for a date' from the phrasing, and the default-to-today behavior signals the no-argument case. There is no explicit when-not guidance and no sibling alternative named (e.g., for a single team's schedule), leaving the agent to infer selection.

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