Skip to main content
Glama

Check a weather word puzzle guess

weather_word_puzzle_guess
Read-onlyIdempotent

Use this for each word the player guesses in the daily word puzzle in Weather With Attitude started with weather_word_puzzle_start. Send the puzzle number, every earlier guess in this game in order, and the new guess. Returns every guess marked letter by letter (right letter in the right place, right letter in the wrong place, or not in the word) and a short comment on the guess. A guess has to be letters only and the same length as the answer; a guess that is not is returned with a reason and does not count. The answer is returned only when the game ends: a correct guess or the sixth miss. Nothing is stored on the server.

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": {
      "puzzle_number": "<puzzle_number>",
      "guess": "<guess>"
    },
    "name": "weather_word_puzzle_guess"
  }
}

Input Schema

NameRequiredDescriptionDefault
guessYesThe word the player just guessed. Letters only; spaces are ignored.
time_zoneNoThe player's IANA time zone, for example "Europe/London" or "America/New_York". Picks the puzzle for their local date. Omit if unknown.
puzzle_numberYesThe puzzle number returned by start_daily_puzzle.
conversation_idNoSet by the Words card so its moves count in the same anonymous usage stats as the chat. Leave it out.
previous_guessesNoEvery earlier guess in this game, oldest first. Empty or omitted before the first guess.
utc_offset_minutesNoThe player's UTC offset in minutes (60 for UTC+1, -300 for UTC-5), used only when the time zone is unknown. Omit both to use UTC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, but the description adds beyond them: statelessness ('nothing is stored on the server'), per-letter result marking, invalid guess handling with a reason, and the fact the answer is revealed only on a correct guess or the sixth miss. That is substantive behavioral context an agent cannot infer from annotations.

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?

Five sentences, front-loaded with the when-to-use, then return shape, then validation, then end conditions. Every sentence carries information; it is slightly long but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must describe returns — and it does, covering the letter-by-letter marking, the short comment, and the answer-reveal condition. For a stateless, idempotent check call, an agent has everything needed to invoke and interpret it.

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 baseline is 3, but the description adds real semantics: it says to send the puzzle number, every earlier guess in order, and the new guess — clarifying that previous_guesses, though optional in schema, is operationally required for correct marking. The letters-only/same-length constraint also reinforces the guess format.

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 ('check each word the player guesses in the daily word puzzle') and anchors it to the start tool, so an agent can distinguish it from weather_word_puzzle_start and weather_word_puzzle_give_up 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 Guidelines5/5

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

Explicitly says to use it for each guess in a game begun with weather_word_puzzle_start, and the invalid-guess clause ('does not count') prevents an agent from aborting on a rejected word. Implicit sibling boundaries (start vs give up) are strongly implied by the referenced flow.

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