Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

nhl: Get stat leaders

nhl_get_stat_leaders
Read-onlyIdempotent

Fetch NHL stat leaders for a chosen category (points, goals, assists, wins) and season, with optional field filtering to focus on needed stats.

Instructions

Get the NHL stat leaders for a given category (points, goals, assists, wins, etc.).

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": "nhl_get_stat_leaders"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
seasonNoSeason identifier, e.g. "20232024"
categoryNoStat category: "points", "goals", "assists", "plusMinus", "gaa", "savePctg", etc. (defaults to "points")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds nothing beyond that: no ranking/limit behavior, no ordering, no indication of how many leaders are returned or how ties are handled. It neither contradicts nor enriches the annotations.

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?

A single, front-loaded sentence with no filler or restatement of the tool title. It is efficient, though its brevity is partly the cause of the gaps noted in other dimensions rather than a virtue of tight writing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety, a fully documented schema and no output schema, the description is minimally sufficient for an agent to invoke the tool. It omits any guidance on season defaults, result size, or relationship to sibling NHL stats tools, so it is adequate rather than complete.

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%, so all three parameters (fields, season, category) are already documented in the schema, including the default for category. The description's category examples duplicate what the schema already lists, adding no syntax, format or interaction detail.

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 (Get) and resource (NHL stat leaders) and scopes it to a category with concrete examples. It is clear on its own, though it does nothing to distinguish itself from analogous tools like mlb_get_league_leaders or openliga_get_top_scorers that an agent may see in the same catalog.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives such as nhl_get_team_stats, nhl_get_player, or nhl_get_standings, nor on prerequisites (e.g. that season is optional, or which categories are valid). The agent is left to infer usage entirely from the name.

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

Deploy Server

Other Tools