Skip to main content
Glama

Game Day Weather

Week board

get_week_board
Read-only

Use when you need the full public board for one NFL week (regular season weeks 1 to 18). Returns every game, including the published call, note, chip, hours, and roof. Pass weekId (YYYY-wNN) or 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.

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

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

A4.4/5.0
Behavior4/5

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

With readOnlyHint and destructiveHint already declaring the safety profile, the description adds genuinely new behavior: what the response contains field-by-field and the edge rule that the current week clamps to 18 after the last kickoff window. Pagination, caching, or rate characteristics are not mentioned, keeping it at 4.

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 sentences, front-loaded with the trigger condition, then the return shape, then the default/edge semantics. No filler or restated title text.

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 single optional parameter with no output schema, the description covers trigger, default resolution, and returned fields well enough to call correctly. Minor gap: it doesn't explicitly state that weeks outside 1–18 are invalid or what an out-of-season request returns.

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 earns an extra point by explaining what 'omit' actually resolves to (the homepage's current week) and the week-18 clamping rule, which the schema pattern alone does not convey.

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?

Names a specific resource (the full public board for one NFL week) and scopes it explicitly to regular season weeks 1–18. The phrase 'every game, including the published call, note, chip, hours, and roof' separates it from the singular get_game sibling without opening either 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?

Opens with an explicit trigger ('Use when you need the full public board for one NFL week') and clarifies the default case (omit weekId for the current week, same as the homepage). It does not name an alternative sibling or state when-not to use it, 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