UnscrambleKey

Find anagrams

find_anagrams

Read-onlyIdempotent

Finds the words that use all of the given letters exactly once, with blank tiles allowed. Returns the anagrams with common words first and their scores, and the number of shorter words the same letters make.

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

Input Schema

Name	Required	Description
`cursor`	No	Opaque cursor from a previous result with the same arguments; absent on the first call.
`letters`	Yes	The rack of letters. Up to 15 characters; _ or ? stands for a blank tile (up to 3 blanks).
`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.7/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful details beyond that: blank tiles are accepted, results are ordered with common words first, scores are included, and a count of shorter words is returned; it does not discuss pagination, though the cursor schema does.

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?

Two compact sentences front-load the core behavior and then summarize results without boilerplate. The return-value sentence partly overlaps the output schema, but the ordering information is useful and the description remains efficient.

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 a fully described schema, a cursor parameter, and an output schema, the description covers the essential behavior and output ordering. It could be slightly more complete by explicitly noting when to choose this over sibling letter-solving tools, but the core call context is present.

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 letters, blanks, scoring, and cursor. The description only confirms blank-tile usage and scoring context and does not add syntax or constraints beyond the schema; baseline 3 is appropriate.

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 states a specific verb ('Finds') and a precise resource/scope ('words that use all of the given letters exactly once'), including blank-tile allowance. It lacks an explicit contrast with similarly named siblings such as unscramble_letters, so it is clear but not fully differentiated.

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 implies use for exact-anagram lookups and mentions blank tiles, but it gives no explicit when-to-use/when-not-to-use guidance or named alternatives. An agent must infer the distinction from the scope statement.

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.