Skip to main content
Glama
Sign In
wordle-mcp

wordle-mcp

by skeeved
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

validate_word

Check if a 5-letter word is accepted as a valid Wordle guess before using it in your game.

Instructions

Check whether a 5-letter word is accepted as a Wordle guess.

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": {
      "word": "<word>"
    },
    "name": "validate_word"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It indicates a read-only validation operation via 'Check', but doesn't detail edge cases, case sensitivity, or the exact return type. This is minimal but not misleading.

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 a single, front-loaded sentence that gets straight to the point. No unnecessary information.

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?

Given the simple tool (one parameter, no output schema), the description is sufficient for understanding the tool's purpose and parameter constraint. It could mention return format, but the verb 'Check' implies a boolean answer.

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?

The schema only defines 'word' as a string with no description. The tool description adds key constraints: the word must be 5 letters and is a Wordle guess. This compensates for the 0% schema coverage.

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?

The description clearly states the tool validates a word against Wordle's accepted guesses. It uses the specific verb 'Check' and names the resource, distinguishing it from sibling tools that suggest or start words.

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

Usage Guidelines4/5

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

The description implies the tool is for verifying whether a specific word is a valid Wordle guess. It doesn't explicitly mention when not to use it or alternatives, but the context of validation versus suggestion is clear.

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

Deploy Server

Other Tools