UnscrambleKey

List words

word_list

Read-onlyIdempotent

Lists the dictionary words of a given length, or that start with, end with or contain given letters, in popularity order with common words first. Returns a page of words with their scores, the counts and a link to the matching list page on unscramblekey.com.

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

Input Schema

Name	Required	Description
`cursor`	No	Opaque cursor from a previous result with the same arguments; absent on the first call.
`length`	No	Exact word length.
`scoring`	No	Points system: scrabble (default) or wwf for Words With Friends.
`contains`	No	Letters the word contains in a row.
`ends_with`	No	Letters the word ends with.
`starts_with`	No	Letters the word starts with.

Output Schema

Name	Required	Description	Default
`id`	No
`url`	No
`kind`	No
`view`	Yes
`items`	Yes
`total`	Yes
`common`	No
`filters`	No
`request`	Yes
`scoring`	No
`overview`	No
`pageSize`	Yes
`nextCursor`	Yes
`continuation`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, but the description adds ordering semantics ("popularity order with common words first") and result paging, which the annotations cannot express. It stops short of describing page size limits or how to detect the last page, so it is useful but not exhaustive.

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 tightly written sentences, with the core capability front-loaded before the return description. The second sentence partially restates what the output schema already covers, which is minor waste rather than bloat.

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?

With a full-coverage schema and an output schema present, the description only needs to convey capability and ordering, both of which it does. Filter combination behavior is the one open question, but nothing essential for correct invocation is missing.

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 every parameter including the cursor and scoring enum is already documented in the schema. The description restates the filter concepts at a high level but adds no syntax, defaults or interaction rules (e.g. whether filters combine) beyond the structured data, so the baseline of 3 applies.

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 ("Lists the dictionary words") and enumerates the exact filter modes (length, starts with, ends with, contains), so an agent can tell what it returns without opening the schema. It does not explicitly contrast itself with siblings such as find_anagrams or solve_pattern, which keeps it short of a 5.

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?

Usage is implied by the filter set rather than stated: an agent can infer this is the tool for prefix/suffix/substring or fixed-length browsing. There is no explicit when-to-use, when-not-to-use, or named alternative, so guidance remains inferential.

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.