Skip to main content
Glama

Game Day Weather

FLAG and WATCH

get_flags
Read-only

Use when you need every game whose published call is FLAG or WATCH, including domes. Optional weekId; omit it for the current week. Returns those games. For an outdoor kick-time checklist before Sunday lock, use get_sunday_lock_sheet.

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

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.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds the 'including domes' scope nuance, which is real context, but says nothing about result ordering, pagination, or what 'published call' means operationally. For a simple filtered read, this is adequate but not rich.

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

Conciseness4/5

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

Front-loaded with the usage trigger, then parameters, then the sibling pointer across three short sentences. The sentence 'Returns those games' is near-redundant, but nothing else is wasted.

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?

A one-optional-parameter, read-only list tool with no output schema and full annotation coverage — the description is sufficient to call it correctly. Only the result shape and any ordering are left implicit, which is a minor gap for a tool returning game records.

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 coverage is 100%; the schema already documents the YYYY-wNN pattern and the 'omit for the current week' behavior, and the description only restates the omission default. Baseline 3 applies since the schema does the heavy lifting and the description adds no format or edge-case detail beyond it.

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: every game whose published call is FLAG or WATCH, and explicitly includes domes so the scope is unambiguous. It is clearly distinguished from get_sunday_lock_sheet, which is named as a different tool for a different need.

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?

Opens with 'Use when you need...' and gives the exact selection condition (published call of FLAG or WATCH). It covers the optional weekId ('omit it for the current week') and routes the agent to get_sunday_lock_sheet for the outdoor kick-time checklist case, so when-not and alternatives are both present.

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