OnlineCyberTools MCP (280+ filterable tools)

text_lorem_ipsum_variations

Read-only

Generate themed placeholder text in vocabularies like bacon, cupcake, or pirate. Choose output as words, sentences, or paragraphs for design mockups.

Instructions

Generate Themed Lorem Ipsum Placeholder Text. Generate themed placeholder text in one of seven vocabularies (classic Lorem Ipsum, bacon, cupcake, pirate, Shakespeare, tech, medical) as words, sentences, or paragraphs. Use this when you want a non-Latin themed vocabulary; use text_lorem_ipsum instead for plain Lorem Ipsum with HTML list output. Output is RANDOM and varies per call (words and sentence lengths are picked at random), so repeat calls return different text. Read-only, non-destructive, pure local compute (no network or persistence). Rate limited to 60 requests/minute for anonymous callers. Returns the generated text plus word/sentence/paragraph/character stats and the resolved generation options.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	Vocabulary theme for the placeholder text.	lorem
`format`	No	Output unit. Unrecognised values fall back to paragraphs.	paragraphs
`count`	No	How many words/sentences/paragraphs to generate; clamped to 1-50.
`startWithTraditional`	No	When true, begin output with the canonical "Lorem ipsum dolor sit amet..." line (consuming part of count).

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No	True when generation succeeded.
`result`	No	The generated placeholder text.
`stats`	No	Text and generation statistics.
`options`	No	Echoed effective options plus the list of available themes.

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: +3
```

addedInput schema / properties / count / description

Added value: +"How many words/sentences/paragraphs to generate; clamped to 1-50."

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

addedInput schema / properties / format / description

Added value: +"Output unit. Unrecognised values fall back to paragraphs."

addedInput schema / properties / format / enum

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

addedInput schema / properties / startWithTraditional / default
```
Added value: +false
```

addedInput schema / properties / startWithTraditional / description

Added value: +"When true, begin output with the canonical \"Lorem ipsum dolor sit amet...\" line (consuming part of count)."

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

addedInput schema / properties / type / description

Added value: +"Vocabulary theme for the placeholder text."

addedInput schema / properties / type / enum

Added value: +[
+  "lorem",
+  "bacon",
+  "cupcake",
+  "pirate",
+  "shakespeare",
+  "tech",
+  "medical"
+]

removedInput schema / required

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "options": {
+      "description": "Echoed effective options plus the list of available themes.",
+      "properties": {
+        "availableTypes": {
+          "description": "All selectable vocabulary themes.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "count": {
+          "description": "Clamped count used.",
+          "type": "integer"
+        },
+        "format": {
+          "description": "Resolved output unit.",
+          "type": "string"
+        },
+        "startWithTraditional": {
+          "description": "Whether the traditional opener was prepended.",
+          "type": "boolean"
+        },
+        "type": {
+          "description": "Resolved vocabulary theme.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "result": {
+      "description": "The generated placeholder text.",
+      "type": "string"
+    },
+    "stats": {
+      "description": "Text and generation statistics.",
+      "properties": {
+        "generation": {
+          "description": "Resolved generation settings.",
+          "properties": {
+            "format": {
+              "description": "Resolved output unit.",
+              "type": "string"
+            },
+            "requestedCount": {
+              "description": "Clamped count used.",
+              "type": "integer"
+            },
+            "startWithTraditional": {
+              "description": "Whether the traditional opener was prepended.",
+              "type": "boolean"
+            },
+            "type": {
+              "description": "Resolved vocabulary theme.",
+              "type": "string"
+            },
+            "vocabularySize": {
+              "description": "Number of words in the chosen vocabulary.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "text": {
+          "description": "Counts derived from the generated text.",
+          "properties": {
+            "characters": {
+              "description": "Total character count.",
+              "type": "integer"
+            },
+            "charactersWithSpaces": {
+              "description": "Character count including spaces.",
+              "type": "integer"
+            },
+            "charactersWithoutSpaces": {
+              "description": "Character count excluding spaces.",
+              "type": "integer"
+            },
+            "paragraphs": {
+              "description": "Number of paragraphs (blank-line separated).",
+              "type": "integer"
+            },
+            "sentences": {
+              "description": "Count of sentence-ending punctuation.",
+              "type": "integer"
+            },
+            "words": {
+              "description": "Number of word tokens.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when generation succeeded.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description discloses randomness of output, read-only nature, pure local compute, and rate limiting (60 req/min for anonymous). Annotations already indicate readOnlyHint=true and destructiveHint=false, and the description adds valuable behavioral context without contradiction.

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?

The description is well-structured, starting with purpose, then details, then sibling comparison, then behavioral notes. Every sentence adds value, though it could be slightly more concise by merging some sentences.

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?

Given the tool's complexity (4 params, enums, output schema), the description covers generation behavior, output content (text + stats), and constraints (randomness, rate limit). It is complete for selecting and invoking the tool correctly.

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% with descriptions for all 4 parameters. The description adds minimal additional semantics beyond enumerating themes and formats already available in the schema. Baseline of 3 is appropriate.

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 themed Lorem Ipsum placeholder text with specific vocabularies and formats. It explicitly differentiates itself from sibling tool text_lorem_ipsum by mentioning themed vs plain and output format differences.

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?

The description explicitly tells when to use this tool (when you want a non-Latin themed vocabulary) and when to use the sibling tool text_lorem_ipsum (for plain Lorem Ipsum with HTML list output). This is clear and actionable.

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

Deploy Server