Skip to main content
Glama

Narrow down a word guess

solve_word_guess
Read-onlyIdempotent

Use this when the user plays a 5-letter word guessing game with green/yellow/gray feedback and wants the remaining possible answers or a strong next guess (word game solver, guess helper). Takes previous guesses with their color feedback (G/Y/-), applies the standard repeated-letter rules, counts the words still possible and lists up to 60 of them, and ranks next guesses by expected information. Supports 4-8 letter variants and hard mode. Does not know today's answer and does not play the game. Do not use for unscrambling letters or crossword patterns.

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": "solve_word_guess"
  }
}

Input Schema

NameRequiredDescriptionDefault
guessesNoGuesses made so far with their color feedback, in order, e.g. [{"word":"CRANE","feedback":"-Y--G"}]. Leave empty for a suggested opening guess.
hard_modeNotrue if every next guess must use all revealed clues (hard mode); then only words that could still be the answer are suggested.
word_lengthNoLetters in the hidden word, e.g. 5 (default: length of the guesses, else 5).

Output Schema

NameRequiredDescriptionDefault
modeYes
moreYes
noteYes
cluesYes
totalYes
solvedYes
guessesYes
candidatesYes
word_lengthYes
best_guessesYes
common_totalYes
guesses_scoredYes
scored_againstYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that repeated-letter rules are applied, that the list is capped at 60 words, that next guesses are ranked by expected information, that 4-8 letter variants and hard mode are supported, and that it neither knows today's answer nor plays the game. The annotations already cover safety/idempotency, so these operational details are pure added value.

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 dense sentences, front-loaded with the trigger, then behavior, then exclusions. No filler and no repetition of the title.

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?

Complete for this tool's complexity: the return contents (count, up to 60 candidates, ranked guesses) are described, an output schema exists so exact shape need not be, and scope limits (no answer lookup, no gameplay) are stated.

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%, so parameter meanings are already fully documented. The description restates the G/Y/- notation and hard-mode semantics without adding format or edge-case detail beyond the schema; baseline 3 applies.

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 ('solve a 5-letter word guessing game', returns remaining candidates plus a ranked next guess) and explicitly differentiates from siblings by ruling out unscrambling and crossword patterns. An agent can select it without opening the 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?

Gives an explicit trigger ('user plays a 5-letter word guessing game with green/yellow/gray feedback'), the two supported outcomes, and an explicit exclusion ('Do not use for unscrambling letters or crossword patterns') that maps directly onto solve_anagram and solve_word_pattern.

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