Skip to main content
Glama
paladini

devutils-mcp-server

lorem_ipsum

Generate placeholder text for design mockups and content layouts. Specify paragraphs, sentences, or words with customizable counts to fill spaces during development.

Instructions

Generate Lorem Ipsum placeholder text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoType of output: paragraphs, sentences, or wordsparagraphs
countNoNumber of paragraphs/sentences/words to generate

Implementation Reference

  • The handler implementation for the `lorem_ipsum` tool, which generates placeholder text based on requested type (paragraphs, sentences, or words) and count.
    async ({ type, count }) => {
      const loremWords = [
        "lorem", "ipsum", "dolor", "sit", "amet", "consectetur", "adipiscing",
        "elit", "sed", "do", "eiusmod", "tempor", "incididunt", "ut", "labore",
        "et", "dolore", "magna", "aliqua", "enim", "ad", "minim", "veniam",
        "quis", "nostrud", "exercitation", "ullamco", "laboris", "nisi",
        "aliquip", "ex", "ea", "commodo", "consequat", "duis", "aute", "irure",
        "in", "reprehenderit", "voluptate", "velit", "esse", "cillum",
        "fugiat", "nulla", "pariatur", "excepteur", "sint", "occaecat",
        "cupidatat", "non", "proident", "sunt", "culpa", "qui", "officia",
        "deserunt", "mollit", "anim", "id", "est", "laborum", "at", "vero",
        "eos", "accusamus", "iusto", "odio", "dignissimos", "ducimus",
        "blanditiis", "praesentium", "voluptatum", "deleniti", "atque",
        "corrupti", "quos", "dolores", "quas", "molestias", "excepturi",
        "obcaecati", "cupiditate", "provident", "similique", "explicabo",
        "nemo", "ipsam", "voluptatem", "quia", "voluptas", "aspernatur",
        "aut", "odit", "fugit", "consequuntur", "magni",
      ];
    
      const randomWord = (i: number): string =>
        loremWords[(i * 7 + 13) % loremWords.length];
    
      const generateSentence = (idx: number): string => {
        const length = 8 + (idx % 7);
        const words = Array.from({ length }, (_, i) => randomWord(idx * 20 + i));
        words[0] = words[0].charAt(0).toUpperCase() + words[0].slice(1);
        return words.join(" ") + ".";
      };
    
      const generateParagraph = (idx: number): string => {
        const sentenceCount = 4 + (idx % 4);
        return Array.from({ length: sentenceCount }, (_, i) =>
          generateSentence(idx * 10 + i)
        ).join(" ");
      };
    
      let text: string;
      if (type === "words") {
        text = Array.from({ length: count }, (_, i) => randomWord(i)).join(" ");
      } else if (type === "sentences") {
        text = Array.from({ length: count }, (_, i) =>
          generateSentence(i)
        ).join(" ");
      } else {
        text = Array.from({ length: count }, (_, i) =>
          generateParagraph(i)
        ).join("\n\n");
      }
    
      return { content: [{ type: "text" as const, text }] };
    }
  • The registration of the `lorem_ipsum` tool using `server.tool` and schema definition for its inputs.
    // Lorem Ipsum generator
    server.tool(
      "lorem_ipsum",
      "Generate Lorem Ipsum placeholder text.",
      {
        type: z
          .enum(["paragraphs", "sentences", "words"])
          .default("paragraphs")
          .describe("Type of output: paragraphs, sentences, or words"),
        count: z
          .number()
          .int()
          .min(1)
          .max(50)
          .default(3)
          .describe("Number of paragraphs/sentences/words to generate"),
      },
Behavior2/5

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

No annotations provided, so description carries full burden. It discloses the generation nature (mutation vs read), but lacks details on determinism (random vs fixed output), output format (string vs array), or any rate limits. 'Generate' alone is insufficient behavioral disclosure for an unannotated tool.

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?

Single sentence, five words. Immediately states purpose with no redundancy. Appropriate front-loading for a simple utility tool.

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?

Adequate for a low-complexity tool with 2 well-documented parameters. However, lacks mention of output format (string, array of strings) despite absence of output schema, and could clarify that Lorem Ipsum is pseudo-Latin text commonly used in design mockups.

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%, with both 'type' and 'count' fully documented in the schema. Description adds no parameter-specific guidance, earning baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb 'Generate' and specific resource 'Lorem Ipsum placeholder text'. Implicitly distinguishes from sibling generators like generate_password or generate_uuid by specifying the Latin placeholder text type, though explicit when-to-use guidance vs those tools is absent.

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

Usage Guidelines2/5

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

No guidance provided on when to use this tool versus similar text generation utilities (generate_password, generate_nanoid) or when placeholder text is needed versus real content. No prerequisites or exclusions mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paladini/devutils-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server