Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

lorem-words

Generate a space-separated list of random words for placeholder text, with a configurable count or min/max range.

Instructions

Generates a space separated list of words.

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

Input Schema

NameRequiredDescriptionDefault
countNoThe number of words to generate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden, and it does add the one fact that matters most for a generator without an output schema: the result is a space-separated list. It does not say what the default count is when count is omitted, what the word pool or randomness characteristics are, or whether any limits apply — relevant gaps given zero annotation coverage.

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 front-loaded sentence with no filler or redundancy, which is well matched to a one-parameter utility. It is efficient, though it spends its only sentence on output format rather than on routing or defaults.

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?

For a trivial one-optional-parameter generator with full schema coverage and no output schema, the description covers the essential unknown — the return shape — so an agent can call it correctly. The default behavior when count is omitted is the remaining unexplained detail, which keeps it short of a 5.

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 already explains count including the min/max object form, so the baseline of 3 applies. The description adds no filtering hints beyond the fact that words are space-separated, which is about output rather than the parameter itself.

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 ("Generates") and resource ("a space separated list of words"), so the output type and shape are immediately clear. It implicitly distinguishes itself from the singular sibling lorem-word through "list," but never names it or any other alternative explicitly.

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 versus lorem-word, lorem-sentence, lorem-text, or word-words. An agent must infer the distinction from the noun in the name alone, with no stated conditions, exclusions, or recommended alternatives.

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