Skip to main content
Glama

Games

get_games
Read-onlyIdempotent

Use when querying past or future games with filters. Returns scores, teams, venue, and game metadata. For upcoming-only games, prefer get_schedule (2 cr) instead. Costs 5 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_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoTeam abbreviation to filter (home or away)
limitNoMax results (default 100)
leagueNoLeague. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl, ahl, ushl.
seasonNoSeason ID, 8-digit (e.g. 20242025 for 2024-25). 2024-25 and 2024-2025 also accepted.
date_toNoEnd date (YYYY-MM-DD)
date_fromNoStart date (YYYY-MM-DD)
game_typeNoFilter by game type
game_stateNoFilter by game state. FINAL and OFF both mean finished and return the same games; FUT is scheduled, LIVE in progress.

Output Schema

NameRequiredDescriptionDefault
noteNo
countYes
gamesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / note
      Added value: +{
      +  "type": "string"
      +}
  2. 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"
      +]
  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, whl, qmjhl, echl."
    • changedInput schema / properties / league / enum
      Previous value: -[
      -  "nhl",
      -  "pwhl"
      -]New value: +[
      +  "nhl",
      +  "pwhl",
      +  "ohl",
      +  "whl",
      +  "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. Changed1 schema field changed
    • changedInput schema / properties / game_state / description
      Previous value: -"Filter by game state"New value: +"Filter by game state. FINAL and OFF both mean finished and return the same games; FUT is scheduled, LIVE in progress."
  6. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is covered. The description adds genuinely useful context the annotations don't carry: the credit cost of the call and the cost of the cheaper alternative. It stops short of noting result-set size or pagination behavior, which the limit param only partially implies.

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?

Three short sentences: trigger, return contents, then the alternative with its cost. The most decision-relevant information (when to use, cheaper sibling) is front-loaded and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full schema coverage, the description needn't explain return shapes or parameter formats, and it correctly spends its words on routing and cost. The one small gap is that it doesn't hint at default result volume (limit default 100, max 500), which matters for an agent deciding whether to paginate.

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 each of the 8 params carries its own explanation, including enum semantics for game_state. The description adds nothing param-specific beyond the phrase 'with filters', so the baseline 3 applies.

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 ('querying') and resource ('past or future games with filters') and immediately lists what comes back: scores, teams, venue, and metadata. It explicitly names the sibling get_schedule as the different option for upcoming-only games, so an agent can distinguish it 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 Guidelines5/5

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

Gives a positive trigger ('querying past or future games with filters') and a concrete routing rule ('For upcoming-only games, prefer get_schedule'). It even supplies the cost trade-off (2 vs 5 credits) that an agent needs to make that choice.

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.