Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

lorem-paragraphs

Generate a specified number of placeholder paragraphs for testing, layouts, or mockups. Set paragraph count or range and optional separator.

Instructions

Generates the given number of paragraphs.

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

Input Schema

NameRequiredDescriptionDefault
separatorNoThe separator to use.
paragraphCountNoThe number of paragraphs to generate.

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 provided, so the description carries the full disclosure burden, yet it says nothing about what is returned (a single string? an array?), how the separator affects output, or whether generation is randomized. Only the bare fact of generation is disclosed, which is minimal for a tool with zero structured behavioral metadata.

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. Its brevity is efficient, though it borders on under-specification rather than tightness.

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?

The tool is simple and the schema is fully documented, but there is no output schema and the description never indicates the return shape or how separator changes it. For a generator whose whole value is the produced text, that omission leaves a meaningful gap.

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 paragraphCount and separator are documented in the schema, making the baseline 3. The description reinforces only the count parameter ("the given number of paragraphs") and says nothing about the separator or the min/max object form, adding no meaning beyond the schema.

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 gives a specific verb and resource ("Generates ... paragraphs") and states that the count is configurable via the input, so an agent knows the basic operation. It stops short of distinguishing this from close siblings such as lorem-paragraph, lorem-text, or lorem-sentences, so an agent cannot resolve plural-vs-single ambiguity from the text alone.

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, no exclusions, and no named alternative. With siblings lorem-paragraph, lorem-sentences, and lorem-text in the catalog, the definition offers nothing to help choose between them.

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