Skip to main content
Glama

Game Day Weather

What changed

get_changes
Read-only

Use when you need games whose published call, roof, window, or kick-window reading moved since a time you give. Pass since (ISO time). Optional weekId; omit it for the current week. A reading counts at 10 or more rain-chance points, 3 mph sustained wind, 3°F on the low, or any wetField level. Roof changes count when the call holds. Going to final is not a call change. If no snapshot is at or before since, the week's first snapshot is the baseline. Returns those moves. flips lists each published call that left one call and landed on another, with gameId, from, to, and at. since is thursday when the current call differs from the Thursday board, and prior when it differs from the compared snapshot. When that snapshot is the Thursday board, since is thursday. Calls and readings are copied from published boards.

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": {
      "since": "<since>"
    },
    "name": "get_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceYesISO-8601 time. Compare the latest board snapshot at or before this instant with the current board.
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. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the read-only, non-destructive annotations, the description discloses substantive behavior: move-count thresholds, roof-change rules, that going final is not a call change, the baseline fallback when no snapshot precedes 'since', and the structure of 'flips' entries. This gives an agent meaningful operational context without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably front-loaded with the use case and parameters, but it is dense with domain-specific shorthand and repeats schema information. The 'since is thursday...' passage is confusing and appears partly redundant, so not every sentence clearly earns its place.

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 needs to carry more of the return-value burden. It describes 'flips' fields and provenance, but 'Returns those moves' does not specify the full shape or fields for non-flip move entries, leaving the output contract partially unclear.

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?

The schema already documents both parameters at 100% coverage, so the baseline is 3. The description adds useful semantics for 'since', especially the baseline fallback when no snapshot is at or before the given time, though the later sentence about 'since is thursday' / 'prior' is ambiguous rather than clarifying.

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 purpose: games whose published call, roof, window, or kick-window reading moved since a given time. It is clear what the tool returns, but it does not explicitly distinguish this from siblings such as get_call_history or get_week_board.

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?

The opening 'Use when...' gives a clear usage condition, and it explains that 'since' is required while 'weekId' is optional and defaults to the current week. It stops short of naming alternatives or stating when not to use this tool.

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