Skip to main content
Glama

Unscramble letters

solve_anagram
Read-onlyIdempotent

Use this when the user wants to unscramble letters or find all words that can be made from a set of letters (word unscrambler, anagram solver, letter-tile word finder), optionally with blank tiles (? or *) and filters for length, starts with, ends with, or contains. Returns dictionary matches grouped by length with counts (every match is counted; up to 25 words are listed per length) and tile points (standard letter values, no board bonuses). Does not check board placement or define words. Do not use for crossword patterns with known letter positions (use solve_word_pattern).

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": {
      "letters": "<letters>"
    },
    "name": "solve_anagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNoOnly words of exactly this many letters, e.g. 5.
lettersYesThe letters to unscramble, e.g. RETAINS. Use ? or * for each blank (wildcard) tile, e.g. QUIZ?ES. Spaces and case are ignored; 2-20 tiles, at most 3 blanks.
containsNoOnly words that contain this run of letters, e.g. QU.
ends_withNoOnly words that end with these letters, e.g. ING.
min_lengthNoShortest word length to include, e.g. 3 (default 2).
starts_withNoOnly words that start with these letters, e.g. RE.
use_all_lettersNotrue to list only words that use every tile (full anagrams), e.g. true for 'what words use all of LISTEN'.

Output Schema

NameRequiredDescriptionDefault
modeYes
noteYes
shownYes
totalYes
blanksYes
groupsYes
filtersYes
lettersYes
top_scoringYes
common_totalYes
full_anagramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the safe-read profile (readOnly/idempotent/non-destructive); the description goes well beyond by disclosing the return shape (matches grouped by length with counts, up to 25 listed per length, tile points with no board bonuses) and hard boundaries ('does not check board placement or define words'). The 'every match is counted' vs 'up to 25 listed' distinction is exactly the kind of truncation behavior an agent needs to avoid misreporting results.

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 trigger, then return behavior, then the exclusion – a sensible ordering with no filler. The opening sentence is long and packs the alias list and all filters into one clause chain, which slightly hurts scannability.

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?

For a 7-parameter search tool with an output schema, the description covers trigger, limits, result formatting, and the nearest competing tool. An agent has everything needed to select and call it correctly, and the description does not waste effort re-explaining return fields already in the output schema.

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 description coverage is 100%, so parameters are already fully self-documenting (blanks via ? or *, 2-20 tiles, max 3 blanks, filter fields). The description only summarizes the same filter set and blank-tile convention, adding no format, precedence, or combination guidance 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+resource ('unscramble letters', 'find all words that can be made from a set of letters') and lists the user-facing aliases (word unscrambler, anagram solver, letter-tile word finder). It also names the sibling it is not (solve_word_pattern), so an agent can separate it from alternatives 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?

Explicit trigger ('Use this when the user wants to unscramble letters...') plus explicit exclusion and routing ('Do not use for crossword patterns with known letter positions (use solve_word_pattern)'). Conditions that select the alternative are stated, not inferred.

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