Skip to main content
Glama

NHL player matchup card: what a defense allows to forwards or defensemen

invoke_nhl_player_matchup
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. NHL player matchup card, calculated by BankrollSZN. What one defense allows per game to the player's position group (forwards or defensemen: DK points, shots, goals, assists, blocks, PP points; last 41 games) vs the league average, with rank (N = allows the most), next to the player's own per-game numbers, his last 5 games and his games against that team. Window: each defense's most recent games across seasons, so early-season samples are not tiny. No opponent = his next opponent on the slate. Example: player Macklin Celebrini.

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

Input Schema

NameRequiredDescriptionDefault
playerYesPlayer name.
opponentNoOpponent abbreviation (SJS, CGY). Default tonight's opponent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent read, yet the description still adds real behavior: the first call triggers an approval prompt because the tool was added after connection, and the statistical window is each defense's most recent games across seasons so early-season samples are not tiny. It also discloses the defaulting rule for the opponent. No pagination or latency/rate-limit detail, which keeps it below a 5.

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?

The approval warning is appropriately front-loaded and the example call is placed at the end where it aids invocation. The central sentence is long and parenthesis-heavy (stat lists and window caveat packed into semicolon clauses), which costs some readability but almost every clause carries substantive information.

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

Completeness5/5

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

There is no output schema, so the description must cover return content, and it does thoroughly: the defensive allowance metrics (DK points, shots, goals, assists, blocks, PP points over the last 41 games), the rank scale with direction explained (N = allows the most), and the player-side context (per-game, last 5, games vs that team). Combined with the approval and window notes, an agent has everything needed to call it and interpret results.

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 both parameters are already documented and the baseline is 3. The description refines the opponent default slightly ('his next opponent on the slate' vs the schema's 'tonight's opponent') and clarifies the position group split, but adds no format or abbreviation guidance beyond what the schema provides.

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 resource (NHL player matchup card) and precisely what it computes: what one defense allows per game to the player's position group vs league average, with rank, alongside the player's own per-game, last-5, and head-to-head numbers. That is specific enough to separate it from sibling tools such as invoke_nhl_line_matchups or invoke_nhl_player_index without opening any schema.

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 implied by the content (player-vs-defense matchup research) and reinforced by a concrete example call ('player Macklin Celebrini'), plus a note that omitting the opponent defaults to his next opponent on the slate. However, there is no explicit when-to-use/when-not guidance and no named alternative for adjacent needs (e.g., line-level matchups), leaving the agent to infer the routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources