mcp-image-downloader
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 |
|---|---|
| download_imageC | Download an image from a URL to a specified path |
| optimize_imageC | Create an optimized version of an image |
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 2 tools
The two tools have clearly distinct purposes: one downloads images from external sources, while the other processes existing images for optimization. There is no overlap in functionality, making it impossible to confuse them.
Both tools follow a consistent verb_noun pattern (download_image and optimize_image) with clear, descriptive names. The naming convention is uniform and predictable throughout the set.
With only two tools, the server feels under-scoped for an image downloader domain. Key operations like listing available images, handling errors, or supporting different image formats are missing, making the toolset too minimal for robust agent workflows.
The toolset is severely incomplete for an image downloader domain. It lacks basic CRUD operations such as listing or deleting images, error handling tools, and support for varied input sources or formats, which will likely cause agent failures in practical use.