Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

lorem-sentence

Generate a placeholder sentence with a set word count for UI mockups, tests, or content layout. Produces a capitalized, period-ended word sequence.

Instructions

Generates a space separated list of words beginning with a capital letter and ending with a period.

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

Input Schema

NameRequiredDescriptionDefault
wordCountNoThe number of words that should be in the sentence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose useful output traits (capitalized first letter, trailing period, space-separated words), but says nothing about randomness, determinism, or what happens when wordCount is omitted.

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?

One compact sentence with no wasted words, and the output shape is front-loaded. It is slightly under-specified rather than over-long.

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?

For a simple single-parameter generator with no annotations or output schema, the description covers the produced string's format. It omits the default word count and any note on randomness, which an agent would want before calling it with no arguments.

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?

The single parameter is fully documented by the schema, including a min/max object form, so the baseline is 3. The description adds no meaning about wordCount, such as its default when absent or its effect on sentence length.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ("Generates") and describes the output rather than the resource: it calls the result "a space separated list of words" instead of a lorem/placeholder sentence. An agent can infer the purpose from the name, but the description never mentions placeholder or lorem-ipsum text, and it does not distinguish this from the plural sibling lorem-sentences.

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-sentences, lorem-text, lorem-paragraph, or lorem-words. The description only states the output shape, leaving the choice between sibling generators entirely to inference from their names.

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