Skip to main content
Glama

Game detail

get_game_detail
Read-onlyIdempotent

Use when you need everything about one game: both teams' full info, all betting odds, and the goalies who started, with their time on ice. Requires a game ID (get one from get_games or get_schedule). Odds for every game from 2019-20 on (and part of the 2019 playoffs). Goalie starts are derived from play-by-play, so they are available for played games, not upcoming ones. Costs 10 credits. Prices are market information; no tool places, accepts or tracks wagers.

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": "get_game_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl, ahl, ushl.
game_idYesNHL game ID (e.g. 2025020887)

Output Schema

NameRequiredDescriptionDefault
gameYes
oddsYes
away_teamYes
home_teamYes
goalie_startsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / league / description
      Previous value: -"League. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl."New value: +"League. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl, ahl, ushl."
    • changedInput schema / properties / league / enum
      Previous value: -[
      -  "nhl",
      -  "pwhl",
      -  "ohl",
      -  "whl",
      -  "qmjhl",
      -  "echl"
      -]New value: +[
      +  "nhl",
      +  "pwhl",
      +  "ohl",
      +  "whl",
      +  "qmjhl",
      +  "echl",
      +  "ahl",
      +  "ushl"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / league / description
      Previous value: -"League. Defaults to nhl. One of: nhl, pwhl."New value: +"League. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl."
    • changedInput schema / properties / league / enum
      Previous value: -[
      -  "nhl",
      -  "pwhl"
      -]New value: +[
      +  "nhl",
      +  "pwhl",
      +  "ohl",
      +  "whl",
      +  "qmjhl",
      +  "echl"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / league
      Added value: +{
      +  "description": "League. Defaults to nhl. One of: nhl, pwhl.",
      +  "enum": [
      +    "nhl",
      +    "pwhl"
      +  ],
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world read, so the bar is lower, yet the description still adds cost (10 credits), data coverage windows (odds from 2019-20 onward plus part of the 2019 playoffs), and a derivation caveat explaining why goalie starts are absent for upcoming games. It also clarifies the market-information framing and that no wagering occurs, which no annotation conveys.

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?

Six sentences, front-loaded with the trigger and resource contents, then prerequisites, then coverage limits, then cost, then a scoping disclaimer. Each sentence carries distinct information with no restatement of the title or 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?

Output schema exists so return-shape explanation is unnecessary, and the description still summarizes the key payload (teams, odds, goalies). For a two-parameter read tool it covers prerequisites, coverage boundaries, cost, and interpretation caveats, leaving no material gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, but the description adds provenance value by telling the agent where to source the required game_id. The league parameter and its enum are left entirely to the schema, which is acceptable given the coverage.

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?

The description opens with a specific trigger plus an enumeration of the resource contents: both teams' full info, all betting odds, and starting goalies with time on ice. That level of detail lets an agent distinguish this aggregate game-detail tool from siblings like get_odds, get_goalie_stats, or get_head_to_head without opening a 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?

It states an explicit when-to-use condition ('when you need everything about one game') and names where to obtain the required game ID (get_games or get_schedule). It also bounds applicability with the odds history window and the played-games-only restriction for goalie starts. It stops short of naming the sibling to use when only a subset of the data is needed.

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.