UnscrambleKey

Solve a pattern

solve_pattern

Read-onlyIdempotent

Finds the words that fit a crossword-style pattern such as A_E, where _ is an unknown letter, optionally limited to words whose unknown positions can be filled from the available letters. Returns the matching words with common words first and their scores.

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": {
      "pattern": "<pattern>"
    },
    "name": "solve_pattern"
  }
}

Input Schema

Name	Required	Description
`cursor`	No	Opaque cursor from a previous result with the same arguments; absent on the first call.
`letters`	No	Optional available letters for the unknown positions; _ or ? stands for a blank tile.
`pattern`	Yes	Letters and _ for unknown positions, for example _A_E_. Up to 15 characters.
`scoring`	No	Points system: scrabble (default) or wwf for Words With Friends.

Output Schema

Name	Required	Description	Default
`item`	Yes
`view`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds genuine behavioral context beyond that: matches are returned with common words first and with scores, which tells the agent how to interpret ordering. It says nothing about result volume or the cursor-paging behavior, which would have pushed it higher.

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?

Two sentences, zero filler, and the core purpose plus example is front-loaded before the optional constraint and the return-ordering note. Nothing repeats the schema verbatim.

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?

With an output schema present and full schema coverage, the description need only cover intent and quirks, which it does. The one omission is any hint that results are paginated via the cursor parameter, which matters for a search-style tool that may return many matches.

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 the baseline is 3. The description earns above that by explaining the interaction between pattern and letters – that available letters fill only the unknown positions – which is a semantic constraint the schema's per-parameter text does not spell out, plus the underscore convention.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Finds the words that fit a crossword-style pattern") and makes the input shape concrete with the example _A_E_. The concept of pattern-matching with wildcards is clearly distinct from anagram or Wordle solving, though it never names a sibling to contrast against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It explains the optional narrowing behavior ("optionally limited to words whose unknown positions can be filled from the available letters"), which tells the agent when to supply letters. It gives no explicit guidance on when to prefer this over find_anagrams or unscramble_letters, so the choice among siblings is left to inference from the pattern vocabulary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All UnscrambleKey tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.