Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

lorem-word

Generates a random word matching a specified length or min/max range, with fallback strategies when no exact-length word is available.

Instructions

Generates a word of a specified length.

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": "lorem-word"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNoThe expected length of the word.
strategyNoThe strategy to apply when no words with a matching length are found. Available strategies: 'fail', 'shortest', 'closest', 'longest', 'any-length'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden and does very little: it doesn't say the output is a single random word, that results are nondeterministic, or how a missing match is handled. The failure behavior is only implied by the schema's strategy enum, not disclosed in the description.

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?

A single short sentence, front-loaded with the action and free of filler. It is efficient, though its brevity comes at the cost of under-specification rather than being over-written.

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

Completeness2/5

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

With no annotations and no output schema, the description should clarify the return value and the fact that both parameters are optional (0 required). It never states what happens when length is omitted or what the default strategy is, leaving real gaps for a generator tool.

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 both the length union type and the five strategy enum values are already fully documented in the schema. The description only repeats the notion of length and adds no format or default information beyond it, making 3 the appropriate 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?

States a specific verb and resource ('Generates a word') with scope ('of a specified length'), which is understandable on its own. It does not distinguish itself from the closely named sibling 'lorem-words' (plural), so an agent must infer the singular-vs-multiple distinction.

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 when-to-use or when-not-to-use guidance, and no reference to the plural sibling as an alternative for multi-word output. The agent gets no help deciding between lorem-word and lorem-words.

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