Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

word-words

Generates random space-separated word strings with optional word count or min/max range for fake text generation.

Instructions

Returns a random string containing some words separated by spaces.

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-words"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoThe optional options object or the number of words to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden, and it does disclose the return shape (a single string of words separated by spaces), which implies a pure, side-effect-free read. It does not say where the words come from (English dictionary vs lorem corpus), whether duplicates are possible, or whether output is deterministic.

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 output shape is stated first and nothing is redundant.

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?

This is a simple zero-required-parameter tool with full schema coverage and no output schema, so the description only needs to convey the return shape, which it does. Minor gaps around word source and repetition behavior are acceptable at this complexity.

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%, and the schema fully documents the optional options object with min/max count semantics, so the baseline is 3. The description's phrase 'some words' gestures at the count parameter but adds no meaning beyond what the schema already provides.

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: it returns a random string of space-separated words. An agent can grasp the output shape immediately, but nothing distinguishes it from siblings like lorem-words, word-sample, or the part-of-speech word tools (word-noun, word-verb).

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus lorem-words or the category-specific word generators, and no stated exclusions or prerequisites. Usage is only implied by the tool name and the word 'random'.

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