Skip to main content
Glama

Shot map

get_shot_map
Read-onlyIdempotent

Use when you want shot locations rather than a list of events: every shot attempt with rink coordinates, shot type, strength, shooter and goalie. Filter by game, or by season plus a team or player. Paginated: follow next_offset, since a season runs past one page and pages are chronological. Costs 10 credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_shot_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam abbreviation; use with season
limitNoMax shots per page (default 1000)
leagueNoLeague. Defaults to nhl. One of: nhl, pwhl, ohl, qmjhl, echl, ahl.
offsetNoPagination offset; follow next_offset for a full season
seasonNoSeason ID, 8-digit (e.g. 20242025); use with team
game_idNoNHL game ID
strengthNoStrength filter, e.g. 5v5
game_typeNoWhich games to include: regular (default for a season) or all (default for one game). Shootout attempts are never included.
player_idNoNHL player ID of the shooter

Output Schema

NameRequiredDescriptionDefault
countYes
shotsYes
summaryYes
next_offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / game_type
      Added value: +{
      +  "description": "Which games to include: regular (default for a season) or all (default for one game). Shootout attempts are never included.",
      +  "enum": [
      +    "regular",
      +    "playoff",
      +    "preseason",
      +    "all"
      +  ],
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / league / description
      Previous value: -"League. Defaults to nhl. One of: nhl, pwhl, ohl, qmjhl, echl."New value: +"League. Defaults to nhl. One of: nhl, pwhl, ohl, qmjhl, echl, ahl."
    • changedInput schema / properties / league / enum
      Previous value: -[
      -  "nhl",
      -  "pwhl",
      -  "ohl",
      -  "qmjhl",
      -  "echl"
      -]New value: +[
      +  "nhl",
      +  "pwhl",
      +  "ohl",
      +  "qmjhl",
      +  "echl",
      +  "ahl"
      +]
  3. 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, qmjhl, echl."
    • changedInput schema / properties / league / enum
      Previous value: -[
      -  "nhl",
      -  "pwhl"
      -]New value: +[
      +  "nhl",
      +  "pwhl",
      +  "ohl",
      +  "qmjhl",
      +  "echl"
      +]
  4. Changed1 schema field changed
    • addedInput schema / properties / league
      Added value: +{
      +  "description": "League. Defaults to nhl. One of: nhl, pwhl.",
      +  "enum": [
      +    "nhl",
      +    "pwhl"
      +  ],
      +  "type": "string"
      +}
  5. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/safe, so the description correctly spends its words elsewhere: pagination behavior ('follow next_offset, since a season runs past one page and pages are chronological') and a 10-credit cost. It doesn't mention response shape, but an output schema exists, so that's a minor gap.

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?

Two sentences, front-loaded with the selection condition, then return fields, filter modes, and pagination/cost caveats. No filler.

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?

For a 9-param, zero-required, paginated read tool with an output schema, the description covers selection, filter modes, page-traversal, and cost — everything an agent needs to call it correctly and not truncate results.

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 the baseline is 3; the description adds cross-parameter meaning the schema lacks — that game_id is used alone, while season pairs with team or player_id — which prevents invalid filter combinations.

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?

States a specific verb+resource ('shot locations' / 'every shot attempt with rink coordinates, shot type, strength, shooter and goalie') and explicitly distinguishes itself from get_plays by contrasting 'shot locations rather than a list of events'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit when-to-use condition and names the alternative (event list) it replaces. Also spells out the two accepted query modes — single game, or season plus team/player.

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.