OnlineCyberTools MCP (280+ filterable tools)

text_lorem_ipsum

Read-only

Generate random Lorem Ipsum placeholder text as words, sentences, paragraphs, or bullet lists, in plain text or HTML. Ideal for dummy copy in mockups and layout testing.

Instructions

Generate Random Lorem Ipsum Placeholder Text. Generate random classic Latin lorem ipsum filler text as words, sentences, paragraphs, or a bullet list, in plain text or HTML. Output is non-deterministic (each call uses random selection, so words and lengths vary) except for the optional fixed opening Lorem ipsum dolor sit amet clause. Use this for neutral placeholder/dummy copy in mockups, UI prototypes, and layout testing. Prefer text_lorem_ipsum_variations when you need themed vocabularies (bacon, cupcake, pirate, Shakespeare, tech, medical); prefer data_data_faker or data_sample_data_generator when you need structured fake records (names, emails, rows) rather than prose. Read-only, offline, no auth; rate limited to 60 requests/minute for anonymous callers. Returns the generated text plus character/word counts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	Unit of text to generate. Invalid values fall back to paragraphs.	paragraphs
`count`	No	How many units (words, sentences, paragraphs, or list items) to produce. Clamped to 1-1000.
`startWithLorem`	No	Begin the output with the canonical Lorem ipsum dolor sit amet opening. Any value other than false is treated as true.
`format`	No	Output format. html wraps paragraphs in p tags and lists in ul/li; anything other than html yields plain text.	plain

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No	True when generation succeeded.
`result`	No	The generated lorem ipsum text (plain or HTML per the format parameter).
`stats`	No	Counts for the generated text. Always includes words, characters, charactersNoSpaces; plus paragraphs (type=paragraphs), sentences (type=sentences), or items (type=lists).

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / count / default
```
Added value: +5
```

addedInput schema / properties / count / description

Added value: +"How many units (words, sentences, paragraphs, or list items) to produce. Clamped to 1-1000."

addedInput schema / properties / count / maximum
```
Added value: +1000
```
addedInput schema / properties / count / minimum
```
Added value: +1
```
addedInput schema / properties / format / default
```
Added value: +"plain"
```

addedInput schema / properties / format / description

Added value: +"Output format. html wraps paragraphs in p tags and lists in ul/li; anything other than html yields plain text."

addedInput schema / properties / format / enum
```
Added value: +[
+  "plain",
+  "html"
+]
```
addedInput schema / properties / startWithLorem / default
```
Added value: +true
```

addedInput schema / properties / startWithLorem / description

Added value: +"Begin the output with the canonical Lorem ipsum dolor sit amet opening. Any value other than false is treated as true."

addedInput schema / properties / type / default
```
Added value: +"paragraphs"
```

addedInput schema / properties / type / description

Added value: +"Unit of text to generate. Invalid values fall back to paragraphs."

addedInput schema / properties / type / enum

Added value: +[
+  "words",
+  "sentences",
+  "paragraphs",
+  "lists"
+]

removedInput schema / required

Removed value: -[
-  "type",
-  "count",
-  "startWithLorem",
-  "format"
-]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "description": "The generated lorem ipsum text (plain or HTML per the format parameter).",
+      "type": "string"
+    },
+    "stats": {
+      "description": "Counts for the generated text. Always includes words, characters, charactersNoSpaces; plus paragraphs (type=paragraphs), sentences (type=sentences), or items (type=lists).",
+      "properties": {
+        "characters": {
+          "description": "Total character count (HTML tags stripped first).",
+          "type": "integer"
+        },
+        "charactersNoSpaces": {
+          "description": "Character count excluding spaces.",
+          "type": "integer"
+        },
+        "items": {
+          "description": "List item count (present only when type=lists).",
+          "type": "integer"
+        },
+        "paragraphs": {
+          "description": "Paragraph count (present only when type=paragraphs).",
+          "type": "integer"
+        },
+        "sentences": {
+          "description": "Sentence count (present only when type=sentences).",
+          "type": "integer"
+        },
+        "words": {
+          "description": "Number of words in the output.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when generation succeeded.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and destructiveHint. Description adds non-deterministic nature, optional fixed opening, and rate limits (60 req/min) without contradicting annotations.

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?

Concise, front-loaded with key info (verb, resource, variants), and every sentence adds value. No fluff.

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

Completeness5/5

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

Given 4 parameters, 100% schema coverage, annotations, and output schema existence, the description covers purpose, usage, behavioral traits, and output details (character/word counts) comprehensively.

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 each parameter is described in schema. Description adds minor clarifications like fallback behavior for invalid type and clamping range, but does not significantly enhance understanding beyond schema.

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

Purpose5/5

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

The description clearly states it generates random Lorem Ipsum placeholder text, and distinguishes from siblings by mentioning text_lorem_ipsum_variations for themed vocabularies and data_data_faker/data_sample_data_generator for structured fake records.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool (neutral placeholder/dummy copy in mockups, UI prototypes, layout testing) and when not to, with specific alternative tools named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server