Image Viewer MCP
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 |
|---|---|
| display-imageB | Display an image from the filesystem. Returns the image as base64 data that Claude can render. |
| list-imagesC | Find and list image files in a directory |
| image-infoA | Get detailed information about an image file without loading the full image data |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: display-image renders images, image-info provides metadata, and list-images enumerates files. An agent can easily differentiate between viewing, inspecting, and discovering images.
All tool names follow a consistent verb-noun pattern with hyphens (display-image, image-info, list-images). The naming is predictable and readable, using clear action words aligned with each tool's function.
Three tools is a minimal but reasonable set for an image viewer server, covering core operations (display, info, list). It feels slightly thin but not inadequate, as each tool serves a distinct and essential function.
For an image viewer domain, the tools cover basic viewing and discovery but lack operations like image editing (e.g., resize, crop, filter) or management (e.g., delete, move). This creates minor gaps that agents might need to work around for more advanced tasks.