Skip to main content
Glama

Game Day Weather

by app.gamedayweather
OverviewDiscussionsAdmin

Week board

get_week_board
Read-only

Full public board for one NFL week (regular season weeks 1–18). Optional weekId. Omit it for the current week, the same week as the homepage. After the last Week 18 kickoff window the current week stays on 18. Read call first, then note, then chip and hours. call is the weather call. chip is the kickoff ±2h threshold check and does not replace the call. A posted DOME call displays chip.level as DOME unless the roof is confirmed open (open, with a source and an announcement time). afterTip is a quiet note, not a flag. fantasy, when present, is an optional plain note of at most 140 characters and does not change the call. roof.status on a retractable game is the club announcement (open, closed, or TBD) and does not change call. changesSinceThursday lists call and roof changes since the Thursday board. Free for agents and AI answers with attribution. Not for model training.

Input Schema

NameRequiredDescriptionDefault
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. Changed2 schema fields changed
    • 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

B3.3/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive behavior; the description adds useful field-level behavior, including that call is the weather call, chip is only a threshold check, roof.status is an announcement, and changesSinceThursday is a change list. It also notes attribution/training restrictions, though it omits rate-limit or auth details.

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

Conciseness2/5

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

The purpose is front-loaded, but the rest is a dense run-on sequence of field notes with unclear ordering. For a one-parameter read tool, several sentences are hard to parse and do not earn their place cleanly.

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?

There is no output schema, so the description must explain return values; it covers several important fields and caveats but does not give the overall board structure or fully enumerate all returned fields. It is adequate but incomplete for a rich board response.

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% and weekId already documents the pattern and omission behavior. The description adds useful context: regular-season weeks are 1–18 and the current week remains on 18 after the last kickoff window.

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?

States a specific verb/resource: the full public board for one NFL week, with regular-season range and current-week default. It does not explicitly contrast this tool with siblings such as get_changes, so it falls short of a 5.

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

Usage Guidelines2/5

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

Explains the weekId default behavior when omitted, but gives no explicit when-to-use/when-not guidance or alternatives among sibling tools. An agent must infer that this is the general weekly-board read rather than a specialized history/change/flag call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Game Day Weather toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources