mcp-image-generator
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 |
|---|---|
| generate_imageA | Generates and returns an image based on the provided promptUse this tool when you need to generate an image based on a promptThe image will be returned as a base64 encoded string |
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 between tools. The single tool 'generate_image' has a clear and distinct purpose that cannot be confused with any other tool in this set.
The single tool name 'generate_image' follows a clear verb_noun pattern. Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate.
A single tool is too few for a server named 'mcp-image-generator', which suggests a broader scope for image generation tasks. While the tool covers basic generation, the count feels thin and lacks operations like editing, upscaling, or managing generated images that might be expected.
The tool set is severely incomplete for an image generation domain. It only provides generation, with no coverage for common operations like editing images, adjusting parameters, retrieving generation history, or handling different formats, which will limit agent capabilities and cause workarounds.