Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

lorem-paragraph

Generate a placeholder paragraph with a specified number of sentences for mock content, UI testing, and layout fills.

Instructions

Generates a paragraph with the given number of sentences.

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

Input Schema

NameRequiredDescriptionDefault
sentenceCountNoThe number of sentences to generate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.1/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 full disclosure burden and falls short. It does not say the output is randomized filler text, does not state what happens when sentenceCount is omitted (the parameter is not required), and does not describe the return format.

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?

One front-loaded sentence with zero filler. Nothing is repeated and nothing is buried; the description is exactly as long as its content warrants.

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 one-parameter generator with no annotations and no output schema, the definition covers the core behavior but omits two things an agent would want: the default when sentenceCount is absent and the nature/format of the returned text. Adequate, with clear gaps.

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 coverage is 100%, so the single sentenceCount parameter, including its min/max object variant, is already fully documented in the schema. The description restates that the count controls sentence length but adds no format or interaction detail; baseline 3 applies.

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 names a specific verb and resource: it 'Generates a paragraph' and states the controlling input ('given number of sentences'). That is enough to distinguish it from unrelated siblings, but it never clarifies how it differs from the near-identical lorem-paragraphs (plural) or lorem-text, which is the distinction an agent most needs.

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 guidance and no mention of alternatives. Given siblings named lorem-paragraph, lorem-paragraphs, lorem-sentence, lorem-sentences and lorem-text, an agent gets no signal about which one to pick for a single paragraph versus several.

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