Skip to main content
Glama

Find words by pattern

solve_word_pattern
Read-onlyIdempotent

Use this when the user needs words that fit a pattern of known and unknown letters, such as a crossword answer (C?T, _A_E, 7 letters ending in ING), with optional letters that must or must not appear. Counts every matching dictionary word and lists up to 120 of them, common words first. Does not solve clues by meaning or look up definitions. Do not use for unscrambling a set of letters (use solve_anagram).

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

Input Schema

NameRequiredDescriptionDefault
lengthNoWord length when there is no pattern, or to check it, e.g. 7 for a 7-letter crossword answer.
patternNoKnown letters with ? (or _ or .) for each unknown letter and * for any run of letters, e.g. C?T, _A_E, ??ANGE, or S*ING. Spaces are ignored.
exclude_lettersNoLetters that must not appear anywhere, e.g. AEIO.
include_lettersNoLetters that must appear somewhere (repeat a letter to require it twice), e.g. RS.

Output Schema

NameRequiredDescriptionDefault
modeYes
moreYes
noteYes
totalYes
wordsYes
filtersYes
patternYes
by_lengthYes
common_totalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful output behavior beyond annotations: it counts every matching dictionary word and returns up to 120 results, common words first. It does not mention other operational details such as case handling or performance, but the key behavioral expectations are covered.

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?

The description is compact and front-loaded: intended use comes first, concrete examples follow, and exclusions/alternatives are placed at the end. Every sentence contributes useful selection or behavior information.

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?

Given full schema descriptions, annotations, and an output schema, the definition is complete enough for an agent to choose and invoke the tool correctly. It also adds result-count and ordering context plus explicit out-of-scope cases.

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 the schema already documents all four parameters in detail. The description reinforces pattern semantics and the must/must-not letter concept, but adds little syntax or format detail beyond what the schema provides; baseline 3 is appropriate.

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: finding words matching known/unknown letter patterns. The examples (C?T, _A_E, 7 letters ending in ING) make the exact operation concrete, and the exclusion of clue-solving and anagram use distinguishes it from siblings.

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 when to use it (crossword-style letter patterns with optional required/excluded letters), when not to use it (meaning-based clue solving, definitions), and names the correct alternative for anagram unscrambling (solve_anagram).

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