MCP Image Placeholder 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 |
|---|---|
| image_placeholderA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
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 ambiguity or overlap with other tools. The tool's purpose is clearly defined and distinct by default.
The single tool name 'image_placeholder' follows a clear and consistent verb_noun pattern. Since there is only one tool, naming consistency is inherently perfect.
A single tool for an image placeholder server feels thin and limited in scope. While it serves a specific purpose, it lacks related operations like listing available providers or generating images with additional parameters, making it borderline too few for practical use.
The tool covers the core functionality of generating placeholder images with basic parameters. However, there are notable gaps, such as no tools for retrieving image metadata, managing providers, or handling errors beyond parameter validation, which limits the server's utility.