Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

nhl: Get game landing

nhl_get_game_landing
Read-onlyIdempotent

Retrieve NHL game landing page data by game ID, including game summary, three stars, scoring plays, and related details for quick game analysis.

Instructions

Get the game landing page data for an NHL game. Includes summary, three stars, scoring plays, and more.

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_get_game_landing"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
game_idYesNHL game ID (e.g. 2023020001)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds a content overview (summary, three stars, scoring plays, and more) beyond the annotations, but it still does not describe return format, pagination, or any limitations.

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 two short sentences and front-loads the core purpose. 'And more' is slightly vague, but overall there is no wasted text.

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?

With no output schema, the description gives some useful content overview but omits differentiation from sibling NHL game endpoints and when to use this one. It is adequate but leaves clear gaps for an agent deciding among similar tools.

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%, and both parameters are documented in the input schema. The description adds no additional parameter meaning or syntax beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource ('Get the game landing page data for an NHL game') and lists some included content. It does not explicitly differentiate from sibling endpoints like nhl_get_game_boxscore or nhl_get_game_play_by_play, so it falls short of a 5.

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?

The description provides no when-to-use guidance, no prerequisites, and no mention of alternative tools. It only says what the tool does, leaving the agent to infer when to select it over related NHL game endpoints.

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

Deploy Server

Other Tools