Skip to main content
Glama

Lorem Ipsum Generator API - paragraphs, sentences, words, list items

lorem_ipsum_generator
Read-onlyIdempotent

Placeholder text on demand: paragraphs, sentences, words or list items, optional HTML tags and classic start. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/lorem-ipsum-generator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "unit": "p",
      "count": 2
    },
    "name": "lorem_ipsum_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlNoWrap in <p> / <li>
unitNop paragraphs, s sentences, w words, l list itemsp
countNoHow many
classicStartNoStart with Lorem ipsum dolor sit amet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / count / minimum
      Added value: +1
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, and the description adds meaningful context: server-side execution, immediate file deletion, no storage, a 25-call daily free limit, and a paid x402 endpoint. It does not describe the returned text format or error behavior, but it materially improves transparency beyond the annotations.

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 front-loaded with the core purpose and then gives relevant operational details in compact sentences. The pricing URL and per-call cost are slightly promotional but still useful for an agent deciding whether to invoke the paid endpoint.

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?

For a low-complexity generator with four optional parameters and no output schema, the description covers output units, formatting flags, data handling, and rate/payment constraints. It would be stronger if it explicitly stated the return type or output format, but it is otherwise complete enough to invoke 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 description coverage is 100%, and the schema itself documents all four optional parameters including the unit enum and HTML/classicStart flags. The description reinforces those concepts but adds no new syntax, constraints, or defaults beyond what the schema already provides.

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 opens with 'Placeholder text on demand' and enumerates paragraphs, sentences, words, or list items, making the generated resource specific. It also mentions HTML wrapping and classic start options, so an agent can distinguish this from other generator tools such as barcode, password, or QR code generators.

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

Usage Guidelines3/5

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

The description implies usage for placeholder or dummy text and supplies operational details like free daily limits and paid per-call pricing. However, it does not explicitly state when to choose this tool over alternatives or when not to use it, leaving usage guidance at an implied level.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources