Lorem Ipsum MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| imageC | Generate or fetch images from picsum.photos with various options |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| greeting | A simple greeting prompt |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.