Skip to main content
Glama
ssv445

Lorem Ipsum MCP Server

by ssv445
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

lorem-ipsum-mcp

An lorem ipsum MCP server

Installation

Install the package globally with npm:

npm install -g lorem-ipsum-mcp

Or run directly with npx:

npx lorem-ipsum-mcp

Related MCP server: Image Toolkit MCP Server

Usage

The MCP server runs on stdio and is designed to be used as a Model Context Protocol server:

# Run directly if installed globally
lorem-ipsum-mcp

# Run with npx (no installation required)
npx lorem-ipsum-mcp

The HTTP server runs on http://localhost:3001 with the SSE endpoint at http://localhost:3001/sse.

Testing

This project includes comprehensive automated testing using GitHub Actions. For detailed testing information, see docs/TESTING.md.

Available Tools

image

Generate or fetch images from picsum.photos with various options.

Usage Examples:

  • Get URL for a random 200x300 image: image --width 200 --height 300

  • Get image file for a random 200x300 image: image --width 200 --height 300 --output file

  • Get URL for a specific, grayscaled, and blurred image: image --id 870 --grayscale --blur 2 --width 200 --height 300

  • List available images: image --list --page 2 --limit 50

  • Get metadata for a specific image: image --info --id 0

Parameters:

  • --width (integer): The width of the image in pixels

  • --height (integer): The height of the image in pixels

  • --id (string): The ID of a specific image to retrieve

  • --seed (string): A seed for generating a static random image

  • --grayscale (boolean): Apply grayscale filter to the image

  • --blur (integer 1-10): Apply blur filter with specified radius

  • --format (jpg|webp): Image format

  • --output (url|file): Output type - url returns string URL, file returns binary data (default: url)

  • --list (boolean): Fetch list of available images

  • --page (integer): Page number for list results

  • --limit (integer): Number of results per page for list

  • --info (boolean): Fetch metadata for a specific image

Available Tools

1 tool
imageC

Generate or fetch images from picsum.photos with various options

ParametersJSON Schema
NameRequiredDescriptionDefault
blurNoApply blur filter (1-10)
formatNoImage format
grayscaleNoApply grayscale filter to the image
heightNoThe height of the image in pixels
idNoThe ID of a specific image to retrieve
infoNoFetch metadata for a specific image
limitNoNumber of results per page for list
listNoFetch list of available images
outputNoOutput type: url returns string URL, file returns binary dataurl
pageNoPage number for list results
seedNoA seed for generating a static random image
widthNoThe width of the image in pixels

TDQS

C2.9/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 behavioral disclosure. It mentions 'Generate or fetch' and 'various options', but doesn't explain key behaviors like whether it's read-only or mutative, rate limits, authentication needs, or what happens with conflicting parameters (e.g., 'id' vs 'list'). This leaves significant gaps for an agent.

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 a single, efficient sentence that front-loads the core purpose without waste. It's appropriately sized for a tool with many parameters but clear schema coverage, earning its place by summarizing the tool's scope concisely.

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

Completeness2/5

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

Given the tool's complexity (12 parameters, no output schema, no annotations), the description is incomplete. It doesn't address behavioral aspects like mutability, error handling, or output format details, which are crucial for an agent to use it correctly. The schema covers parameters well, but the description fails to compensate for other gaps.

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 description adds minimal meaning beyond the input schema, which has 100% coverage with detailed parameter descriptions. It implies parameters exist ('various options') but doesn't clarify semantics like how 'id', 'list', and 'info' interact. With high schema coverage, the baseline is 3, as the schema does most of the work.

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?

The description states the tool's purpose clearly: 'Generate or fetch images from picsum.photos with various options'. It specifies the verb ('Generate or fetch'), resource ('images'), and source ('picsum.photos'), which is specific and informative. However, it doesn't distinguish from siblings (none provided), so it's not a perfect 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions 'various options' but doesn't specify contexts, exclusions, or prerequisites. Without siblings, it could imply this is the only image tool, but it lacks explicit usage instructions.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool 'image' has a clear, distinct purpose focused on image generation or fetching from picsum.photos.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'image' is straightforward and follows a simple noun pattern.

Tool Count2/5

One tool is too few for most server purposes, as it severely limits functionality and scope. While the tool's description suggests a specific domain (image handling), a single tool feels thin and incomplete for practical use cases.

Completeness2/5

The server appears focused on image operations from picsum.photos, but with only one tool, there are significant gaps. For example, there are no tools for managing images (e.g., delete, update), searching, or handling other aspects of image workflows, making the surface severely incomplete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

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/ssv445/lorem-ipsum-mcp'

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