Skip to main content
Glama
argotdev

NHL MCP Server

by argotdev

get_schedule

Retrieve NHL game schedules for upcoming matches, with options to filter by specific dates or teams using official league data.

Instructions

Get NHL schedule for upcoming games. Can get schedule for a specific date or team.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format (optional, defaults to current week)
teamAbbrevNoTeam abbreviation to get specific team schedule (e.g., TOR, NYR)

Implementation Reference

  • The handler for the 'get_schedule' MCP tool. It checks if a teamAbbrev is provided; if so, fetches the team schedule using getTeamSchedule, otherwise fetches the general schedule using getSchedule. Returns the JSON-stringified schedule data.
    case 'get_schedule': {
      if (parameters.teamAbbrev) {
        const schedule = await client.getTeamSchedule(
          parameters.teamAbbrev as string,
          parameters.season as string | undefined
        );
        return {
          content: [{ type: 'text', text: JSON.stringify(schedule, null, 2) }],
        };
      } else {
        const schedule = await client.getSchedule(parameters.date as string | undefined);
        return {
          content: [{ type: 'text', text: JSON.stringify(schedule, null, 2) }],
        };
      }
    }
  • Input schema definition for the 'get_schedule' tool, defining optional 'date' and 'teamAbbrev' parameters.
    inputSchema: {
      type: 'object',
      properties: {
        date: {
          type: 'string',
          description: 'Date in YYYY-MM-DD format (optional, defaults to current week)',
        },
        teamAbbrev: {
          type: 'string',
          description: 'Team abbreviation to get specific team schedule (e.g., TOR, NYR)',
        },
      },
    },
  • src/index.ts:126-142 (registration)
    Registration of the 'get_schedule' tool in the TOOLS array, which is returned by ListToolsRequestHandler. Includes name, description, and input schema.
    {
      name: 'get_schedule',
      description: 'Get NHL schedule for upcoming games. Can get schedule for a specific date or team.',
      inputSchema: {
        type: 'object',
        properties: {
          date: {
            type: 'string',
            description: 'Date in YYYY-MM-DD format (optional, defaults to current week)',
          },
          teamAbbrev: {
            type: 'string',
            description: 'Team abbreviation to get specific team schedule (e.g., TOR, NYR)',
          },
        },
      },
    },
  • Core helper function getSchedule in NHLAPIClient that fetches the NHL schedule data from the official API for a given date (defaults to today). Called by the tool handler.
    async getSchedule(date?: string): Promise<any> {
      const dateStr = date || new Date().toISOString().split('T')[0];
      return this.fetchJSON(`${NHL_API_BASE}/schedule/${dateStr}`);
    }
  • Supporting helper getTeamSchedule used by the get_schedule handler when teamAbbrev is provided. Fetches team-specific schedule from the NHL API.
    async getTeamSchedule(teamAbbrev: string, season?: string): Promise<any> {
      const seasonStr = season || this.getCurrentSeason();
      return this.fetchJSON(`${NHL_API_BASE}/club-schedule-season/${teamAbbrev}/${seasonStr}`);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the tool can retrieve schedules but doesn't cover key traits like whether it's read-only (implied by 'Get'), rate limits, error handling, or output format. This leaves significant gaps for a tool with no structured safety hints.

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 description is appropriately sized with two sentences that are front-loaded: the first states the core purpose, and the second adds parameter context. There's no wasted text, though it could be slightly more structured for clarity.

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?

Given the tool's low complexity (2 optional parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and parameter hints but lacks details on behavior, output, or integration with siblings, leaving room for improvement in completeness.

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 the input schema fully documents both parameters (date and teamAbbrev) with descriptions. The description adds minimal value by hinting at optionality ('Can get schedule for a specific date or team') but doesn't provide additional semantics beyond what the schema already states, meeting the baseline.

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 tool's purpose: 'Get NHL schedule for upcoming games.' It specifies the resource (NHL schedule) and scope (upcoming games). However, it doesn't explicitly differentiate from siblings like 'get_live_games' or 'get_game_details,' which might also retrieve schedule-related data, so it misses the top score.

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?

The description provides implied usage by mentioning 'Can get schedule for a specific date or team,' suggesting when to use optional parameters. But it lacks explicit guidance on when to choose this tool over alternatives like 'get_live_games' for current games or 'get_game_details' for specific matchups, and no exclusions are stated.

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