Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Random words for games

random_words
Read-onlyIdempotent

Random English words for word games, filtered by part of speech, length, first letters and difficulty, and repeatable with a seed. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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

Input Schema

NameRequiredDescriptionDefault
posNoOnly words that can be this part of speech.
safeNoKid-safe words only (best effort, see safeNote).
seedNoWhole number 0-4294967295 for a repeatable list.
countNoHow many words, 1-100 (default 1).
levelNoeasy, common (default) or all.
lengthNoExact length, 2-15.
maxLengthNoLongest length (default 15).
minLengthNoShortest length (default 2).
startsWithNoFirst 1-3 letters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only that results are repeatable via a seed, which is already documented in the schema; it says nothing about list size limits, default behavior when no filters are given, or what the response looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded and dense with relevant capability information. The second sentence is pure promotional link text with UTM parameters that does not help an agent select or invoke the tool and dilutes an otherwise tight definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Nine optional parameters and no output schema mean the description should at least sketch the return shape (a list of words, length of list, effect of count). It covers the input surface adequately via the schema but leaves output expectations and default behavior unstated.

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 every parameter is already documented with ranges, enums and defaults. The description's filter summary mirrors the schema rather than adding semantics such as how length interacts with minLength/maxLength or how 'safe' best-effort behaves. Baseline 3 applies when the schema carries the load.

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?

States a specific resource and behavior: 'Random English words for word games', then enumerates the filter dimensions (part of speech, length, first letters, difficulty) and seed-based repeatability. An agent can tell this generates word lists rather than defining or relating words, though it never names the nearby siblings (related_words, define_word) to sharpen the distinction.

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?

'for word games' implies a usage context, and the filter list hints at when to reach for it, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool. Guidance is inferred rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources