SmartTools

Lorem ipsum generator

lorem_ipsum

Generate placeholder lorem ipsum text by paragraphs, sentences or words. Runs on smart-tools.xyz.

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

Input Schema

Name	Required	Description
`unit`	No	paragraphs (default), sentences or words
`count`	No	How many units to generate (default 3)
`locale`	No	Language for the source_url link (default en)
`start_lorem`	No	Begin with the classic 'Lorem ipsum dolor sit amet…' (default true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 17, 2026

TDQS

B3.4/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 burden of disclosure, but it only states the basic function and a deployment note ('Runs on smart-tools.xyz'). It does not disclose return format, side effects, or error behavior.

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 a single sentence front-loaded with the core purpose, followed by a brief deployment note. It is concise, though the 'Runs on smart-tools.xyz' clause adds marginal value and could be considered unnecessary.

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

Completeness3/5

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

For a simple generator with full schema coverage, the description conveys the essential purpose and unit options. However, without an output schema, it does not clarify the exact return shape (e.g., string vs. array) or potential limitations, leaving some ambiguity.

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?

The schema covers all 4 parameters with descriptions, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides, but it does not need to compensate since coverage is 100%.

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 a specific action ('generate') and resource ('placeholder lorem ipsum text'), and distinguishes the tool from siblings by specifying the output units (paragraphs, sentences, or words). This is sufficient to differentiate it among the many generator tools.

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?

No explicit when-to-use or alternative tools are mentioned. However, the purpose is self-evident for creating placeholder text, so usage is implied rather than explicitly guided.

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

All SmartTools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?