UnscrambleKey

Solve Wordle

solve_wordle

Read-onlyIdempotent

Solves a Wordle position from the guesses made and the colour of each letter. Returns the words still possible with common words first, the ten best next guesses and the letters ruled out, or a note when the clues cannot all be true.

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": {
      "guesses": "<guesses>"
    },
    "name": "solve_wordle"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	Opaque cursor from a previous result with the same arguments; absent on the first call.
`guesses`	Yes	The guesses made so far, in order.

Output Schema

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

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 cover safety: readOnly, idempotent, non-destructive and closed-world. The description adds real behavior beyond them by naming the output shape (possible words with common words first, ten best next guesses, ruled-out letters) and by disclosing what happens when clues are inconsistent. It does not mention the cursor's role in paging, which is left to the schema.

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?

A single front-loaded sentence with no filler: the verb-plus-resource comes first, followed by the concrete return contents. Every clause carries information an agent would otherwise have to infer.

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?

The tool has only two parameters, both fully documented, and an output schema, so the description does not need to explain return values. It still leaves the cursor paging convention and any per-position limits unmentioned, which keeps it short of fully complete.

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 the schema already explains guesses, word, colors and cursor. The description restates the guesses-and-colours concept but adds no format, ordering or validation detail beyond the schema, which makes 3 the right baseline.

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 and resource: 'Solves a Wordle position from the guesses made and the colour of each letter.' The input is clearly a set of Wordle guesses, which separates it from general dictionary tools like find_anagrams or word_list. It does not explicitly name or contrast with solve_pattern, the closest sibling, so it falls short of 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 Wordle framing: feed in guesses with per-letter colours to get remaining candidates. There is no explicit statement of when to prefer this over solve_pattern or when not to use it, and no exclusion of invalid inputs beyond the contradictory-clue note.

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.