Skip to main content
Glama
argotdev

NHL MCP Server

by argotdev

get_game_details

Retrieve comprehensive NHL game information including play-by-play data, scoring plays, and period summaries by providing a specific game ID.

Instructions

Get detailed information about a specific game including play-by-play data, scoring plays, and period summaries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameIdYesThe NHL game ID

Implementation Reference

  • MCP tool handler case that parses parameters, calls NHLAPIClient.getGameDetails(gameId), and returns JSON stringified response.
    case 'get_game_details': {
      const details = await client.getGameDetails(parameters.gameId as number);
      return {
        content: [{ type: 'text', text: JSON.stringify(details, null, 2) }],
      };
    }
  • Tool definition including name, description, and input schema requiring 'gameId' as number.
    {
      name: 'get_game_details',
      description: 'Get detailed information about a specific game including play-by-play data, scoring plays, and period summaries.',
      inputSchema: {
        type: 'object',
        properties: {
          gameId: {
            type: 'number',
            description: 'The NHL game ID',
          },
        },
        required: ['gameId'],
      },
    },
  • Core tool implementation: fetches detailed game play-by-play data from NHL API.
    async getGameDetails(gameId: number): Promise<any> {
      return this.fetchJSON(`${NHL_API_BASE}/gamecenter/${gameId}/play-by-play`);
    }
  • src/index.ts:460-462 (registration)
    Registers the list tools handler which returns the TOOLS array containing get_game_details.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools: TOOLS };
    });
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states what data is returned but doesn't disclose behavioral traits such as whether this is a read-only operation (implied by 'Get'), potential rate limits, authentication needs, error handling, or data freshness. For a tool with no annotations, this leaves significant gaps in understanding how it behaves.

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?

The description is a single, efficient sentence that front-loads the core purpose and lists specific data types. Every word earns its place with no redundancy or fluff, making it easy to scan and understand quickly.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a tool that returns complex data (play-by-play, scoring plays, etc.). It mentions what data is included but doesn't explain return format, structure, or potential limitations. For a detailed query tool, more context on output behavior is needed to be fully helpful.

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% for the single parameter (gameId), so the schema already documents it fully. The description adds no additional meaning beyond what the schema provides (e.g., no examples of valid gameIds or format details). Baseline 3 is appropriate when schema does the heavy lifting, though no extra value is added.

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 clearly states the verb 'Get' and resource 'detailed information about a specific game', specifying the types of data included (play-by-play, scoring plays, period summaries). It distinguishes from siblings like get_schedule (list of games) or get_player_stats (player-focused), though not explicitly named. The purpose is specific but could be more precise about sibling differentiation.

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?

No explicit guidance on when to use this tool versus alternatives. It implies usage for detailed game data, but doesn't mention prerequisites (e.g., needing a valid gameId), exclusions (e.g., not for live games vs. get_live_games), or direct comparisons to siblings like get_schedule for game lists. The context is clear but lacks operational guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/argotdev/nhl-mcp-ts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server