Skip to main content
Glama
argotdev

NHL MCP Server

by argotdev

get_playoff_bracket

Retrieve the current NHL playoff bracket with series matchups, results, and standings to track postseason progress and outcomes.

Instructions

Get current playoff bracket with series information, matchups, and results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seasonNoSeason year (e.g., 2024), defaults to current season

Implementation Reference

  • Core handler function that fetches the NHL playoff bracket data from the official API endpoint using the provided season or current year.
    async getPlayoffBracket(season?: string): Promise<any> {
      const year = season || new Date().getFullYear().toString();
      return this.fetchJSON(`${NHL_API_BASE}/playoff-bracket/${year}`);
    }
  • src/index.ts:143-155 (registration)
    Tool registration in the MCP server's TOOLS array, defining name, description, and input schema.
    {
      name: 'get_playoff_bracket',
      description: 'Get current playoff bracket with series information, matchups, and results.',
      inputSchema: {
        type: 'object',
        properties: {
          season: {
            type: 'string',
            description: 'Season year (e.g., 2024), defaults to current season',
          },
        },
      },
    },
  • MCP server request handler that receives tool call parameters, invokes the NHLAPIClient.getPlayoffBracket method, and formats the response as JSON text.
    case 'get_playoff_bracket': {
      const bracket = await client.getPlayoffBracket(parameters.season as string | undefined);
      return {
        content: [{ type: 'text', text: JSON.stringify(bracket, null, 2) }],
      };
    }
  • Input schema defining the optional 'season' parameter for the tool.
    inputSchema: {
      type: 'object',
      properties: {
        season: {
          type: 'string',
          description: 'Season year (e.g., 2024), defaults to current season',
        },
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It states what data is returned but doesn't disclose whether this is a read-only operation, if it requires authentication, rate limits, error conditions, or how 'current' is determined (e.g., live updates vs. cached data).

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 key data components. Every word earns its place with zero redundancy or unnecessary elaboration.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It lacks details on return format (e.g., structure of bracket data), error handling, authentication needs, or how 'current' interacts with the optional season parameter, leaving significant gaps for agent understanding.

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 schema already documents the single parameter 'season' with its type and default behavior. The description adds no additional parameter semantics beyond implying the bracket is season-specific, which is already covered by the schema.

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 action ('Get') and resource ('current playoff bracket') with specific components ('series information, matchups, and results'). It distinguishes from siblings like get_schedule or get_standings by focusing on playoff brackets, but doesn't explicitly differentiate from tools like compare_seasons that might involve playoff data.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, timing considerations, or comparisons to sibling tools like get_schedule or get_standings that might overlap with playoff information.

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