mcp

Lorem Ipsum

lorem_ipsum

Read-onlyIdempotent

Use this when you need placeholder/filler copy for mockups, tests, or layout. Given a mode ("paragraphs", "sentences", "words", or "formatted") and a count, cycles a fixed built-in Latin corpus to return the same text every time. count is clamped to the mode's max (paragraphs 20, sentences 100, words 500) and defaults to 1 when missing or below 1; "formatted" ignores count and returns a fixed multi-block sample (with count 0). Deterministic: same input, same output. Example: {mode: "words", count: 5} -> text "Lorem ipsum dolor sit amet.", count 5.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode": "<mode>"
    },
    "name": "lorem_ipsum"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	Yes	Unit of generated text. "paragraphs", "sentences", or "words" repeat the corpus up to the requested count; "formatted" returns a fixed multi-block sample as plain text and ignores count.
`count`	No	How many units to generate. Clamped to the mode's max (paragraphs 20, sentences 100, words 500); values below 1 or missing default to 1. Unused for "formatted".

Output Schema

Name	Required	Description
`mode`	Yes	The generation mode used (echoes the requested `mode`).
`text`	Yes	The generated placeholder text. Paragraphs are separated by blank lines; words mode is capitalized and terminated with a period.
`count`	Yes	The effective number of units generated after clamping/defaulting; always 0 for "formatted" mode.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "description": "The effective number of units generated after clamping/defaulting; always 0 for \"formatted\" mode.",
+      "type": "integer"
+    },
+    "mode": {
+      "description": "The generation mode used (echoes the requested `mode`).",
+      "enum": [
+        "paragraphs",
+        "sentences",
+        "words",
+        "formatted"
+      ],
+      "type": "string"
+    },
+    "text": {
+      "description": "The generated placeholder text. Paragraphs are separated by blank lines; words mode is capitalized and terminated with a period.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "mode",
+    "count",
+    "text"
+  ],
+  "type": "object"
+}

AddedJul 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds detailed behavioral context: determinism, parameter clamping (maxes, defaults), and formatted mode behavior. It also provides an example, going well beyond 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?

The description is two concise sentences followed by an example. Every sentence adds value, is front-loaded with the use case, and there is 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 the tool has 2 parameters (one enum), the description covers behavior, edge cases, and an example. Output schema exists, so no need to explain return values. The description is complete for an agent to effectively use the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds extra meaning by explaining enum values further and detailing clamping behavior and defaults, which increases understanding beyond the 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 the tool is for placeholder/filler copy for mockups, tests, or layout. It specifies the verb 'use' and resource 'placeholder/filler copy', and distinguishes from sibling tools (different utilities) by its unique function.

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

Usage Guidelines4/5

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

The description explicitly says when to use the tool ('when you need placeholder/filler copy for mockups, tests, or layout'). It doesn't explicitly state when not to use it, but the context makes it clear given the sibling tools are all different utilities.

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

All mcp tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?