image-reader-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_imagesB | List image files in a specified directory. |
| read_imageA | Reads a specific image file and returns its content as base64. |
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
list_images and read_image are clearly distinct: one discovers images in a directory, the other retrieves the content of a specific image. There is no overlap or ambiguity between them.
Both tool names follow a verb_noun pattern (list_images, read_image), using snake_case consistently. The naming is predictable and easy to infer.
With only two tools, the server feels minimal, which is borderline for a tool set. However, for an image reader, listing and reading are the essential operations, so the count is appropriate for the narrow scope, but still falls into the 'thin' category.
The server's purpose is to read images, and it provides the two core operations: enumerating available images and reading a specific one. There are no obvious gaps for this use case; it covers the full lifecycle of reading (discover then retrieve).