Skip to main content
Glama

Text Analysis & Cleanup Tools (Tanod)

text_lorem

Read-onlyIdempotent

utilpeek: Generate seeded lorem ipsum or English placeholder text. For random values use generate_random. Returns placeholder text: classic lorem ipsum or English filler, in words (at most 10,000), sentences (1,000) or paragraphs (100), deterministic for a seed (echoed back). Input: optional kind, unit, count, seed and start_with_lorem; an empty body gives 3 paragraphs. Typically under 0.3 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day.

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": "text_lorem"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNolorem (Latin-like lorem ipsum, default) or english (common English words).lorem
seedNoRandom seed: the same seed and settings give the same text.
unitNoWhat `count` counts: words, sentences or paragraphs (default).paragraphs
countNoAt most 10,000 words, 1,000 sentences or 100 paragraphs.
start_with_loremNokind=lorem: begin with "Lorem ipsum dolor sit amet".

Output Schema

NameRequiredDescriptionDefault
kindNo
seedNo
textNo
unitNo
countNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
wordsNo
sourceNo
charactersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedInput schema / properties / count / title
      Removed value: -"Count"
    • removedInput schema / properties / kind / title
      Removed value: -"Kind"
    • changedInput schema / properties / seed / description
      Previous value: -"Random seed (default 0): the same seed and settings give the same text."New value: +"Random seed: the same seed and settings give the same text."
    • removedInput schema / properties / seed / title
      Removed value: -"Seed"
    • changedInput schema / properties / start_with_lorem / description
      Previous value: -"kind=lorem: begin with \"Lorem ipsum dolor sit amet\" (default true)."New value: +"kind=lorem: begin with \"Lorem ipsum dolor sit amet\"."
    • removedInput schema / properties / start_with_lorem / title
      Removed value: -"Start With Lorem"
    • removedInput schema / properties / unit / title
      Removed value: -"Unit"
    • removedInput schema / title
      Removed value: -"text_loremArguments"
  2. Changed5 schema fields changed
    • addedInput schema / properties / kind / description
      Added value: +"lorem (Latin-like lorem ipsum, default) or english (common English words)."
    • addedInput schema / properties / seed / description
      Added value: +"Random seed (default 0): the same seed and settings give the same text."
    • addedInput schema / properties / start_with_lorem / description
      Added value: +"kind=lorem: begin with \"Lorem ipsum dolor sit amet\" (default true)."
    • addedInput schema / properties / unit / description
      Added value: +"What `count` counts: words, sentences or paragraphs (default)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "characters": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "count": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "kind": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "seed": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "text": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "unit": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "words": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds substantial behavioral context beyond that: deterministic seeded output, seed echoing, output limits, typical latency, price, and free-call quota.

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 purpose and alternative routing, followed by output and input details. It is information-dense and mostly earns its length, though the pricing and quota details add some bulk beyond the core invocation guidance.

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's simplicity, the existing output schema, and rich annotations, the description is complete enough for correct invocation. It covers purpose, alternative routing, defaults, limits, determinism, and practical constraints such as latency and quota.

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%, so the schema already documents the parameters, enums, defaults, and limits. The description adds some useful meaning, especially that an empty body returns 3 paragraphs and that the seed is echoed back, but much of the parameter information is already present in 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 states a specific verb and resource: generating seeded lorem ipsum or English placeholder text. It explicitly distinguishes the deterministic use case from the sibling generate_random, so an agent can identify the right tool without inspecting schemas.

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?

It gives explicit routing guidance: use this tool for seeded placeholder text and use generate_random for random values. It also clarifies the default behavior when the body is empty, leaving little ambiguity about when this tool applies.

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.