Skip to main content
Glama

Game Day Weather

One game

get_game
Read-only

Use when you need one game's published weather call. Pass team (a code such as BUF or NE) or gameId (such as 2026-w04-ne-buf). Optional weekId; omit it for the current week. A gameId selects that game's week when weekId is omitted. Returns that game plus asOf, stale, and nextUpdate.

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

Input Schema

NameRequiredDescriptionDefault
teamNoNFL team code, such as BUF or NE.
gameIdNoGame id, such as 2026-w04-ne-buf.
weekIdNoWeek id YYYY-wNN, for example 2026-w04. Regular season weeks are 1–18. Omit for the current week.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / gameId / maxLength
      Added value: +40
    • changedInput schema / properties / team / description
      Previous value: -"Team code, such as BUF or NE."New value: +"NFL team code, such as BUF or NE."
    • changedInput schema / properties / weekId / description
      Previous value: -"Week id YYYY-wNN, for example 2026-w04. Omit for the current week."New value: +"Week id YYYY-wNN, for example 2026-w04. Regular season weeks are 1–18. Omit for the current week."
    • addedInput schema / properties / weekId / pattern
      Added value: +"^\\d{4}-w\\d{2}$"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, so the description earns credit for adding return context (asOf, stale, nextUpdate) that matters because there is no output schema. It also explains the weekId/gameId precedence rule. It does not say what happens if neither team nor gameId is supplied, or how ambiguity is resolved.

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?

Four compact sentences, front-loaded with the trigger and then the parameter rules. Nothing 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?

For a 3-param read tool with full schema coverage and no output schema, the description covers selection logic and the key return fields. Missing only edge-case behavior (no team or gameId given, unknown team code).

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 goes further by giving the precedence rule that a gameId selects its own week when weekId is omitted, which the schema does not state. Examples duplicate the schema descriptions rather than extend them.

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 and resource: fetch one game's published weather call. That scope implicitly separates it from list-shaped siblings like get_team_games and get_week_board 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?

"Use when you need one game's published weather call" gives a clear trigger and the two addressing modes (team vs gameId) plus the optional weekId. It never names an alternative tool or says when not to use this one, so it stops short of a 5.

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.

Resources