Skip to main content
Glama

nhl_gamecenter_play_by_play

Read-only

Read the NHL gamecenter play-by-play for one source game ID and return the upstream object with its event sequence, associated game records, teams and time context. game_id is a required 10-digit NHL game ID (get one from nhl_schedule). The upstream event order and fields are preserved without regrouping, derived events or local filtering; an invalid ID is rejected and a malformed or incomplete body is reported as an upstream failure rather than an empty sequence.

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": {
      "game_id": "<game_id>"
    },
    "name": "nhl_gamecenter_play_by_play"
  }
}

Input Schema

NameRequiredDescriptionDefault
game_idYesRequired 10-digit NHL game ID, for example 2026020262. Get one from the schedule resource (nhl_schedule); the upstream gamecenter object is preserved as returned.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond readOnlyHint/openWorldHint: event order and fields are preserved without regrouping or derived events, no local filtering occurs, invalid IDs are rejected, and malformed upstream bodies surface as failures rather than empty sequences. This error and fidelity contract is exactly the kind of context annotations cannot express, and the output schema already covers return structure.

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?

Front-loads the action, resource, and scope in the first sentence, then follows with sourcing and fidelity/error semantics. Every clause is relevant, though the enumerated return components are slightly redundant against the output schema.

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?

For a single-parameter, read-only tool with full schema coverage, an output schema, and open-world annotations, the definition covers sourcing, preservation guarantees, and failure semantics. Nothing an agent needs to select or invoke it correctly is missing.

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 coverage is 100% and the single game_id parameter is fully documented in the schema, including its 10-digit format, example, and sourcing from nhl_schedule. The description largely restates those facts rather than adding syntax or validation detail beyond the structured fields, so baseline 3 applies.

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 verb ('Read'), a specific resource ('NHL gamecenter play-by-play'), explicit scope ('one source game ID'), and the return shape ('upstream object with its event sequence, associated game records, teams and time context'). An agent can distinguish this from nhl_gamecenter_boxscore or other sport play-by-play tools without opening the schema.

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

Usage Guidelines4/5

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

Gives clear precondition guidance by directing the agent to obtain game_id from nhl_schedule, and clarifies the tool's read-only pass-through nature. It does not explicitly name when-not-to-use or contrast with sibling play-by-play tools, so it stops short of a 5.

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.