read-image-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| READ_IMAGE_MCP_CONFIG | No | Path to the configuration JSON file. If not provided, the server looks for read-image-mcp.config.json in the current working directory and then ~/.config/read-image-mcp/config.json. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_imageC | Read an image through an OpenAI-compatible vision model. Supports path, url, base64, and data_url sources. |
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 confusing it with others. The tool's purpose is clearly defined, so an agent can unambiguously select it when needing to read an image.
The single tool name 'read_image' follows a clear verb_noun pattern, which is consistent. There are no other tools to create inconsistencies.
One tool is on the lower end of typical tool counts. While the server's purpose is narrow, a single tool feels thin; however, it is appropriate for the specific functionality provided.
The tool covers all common input methods for images (path, URL, base64, data URL), so there are no obvious gaps in functionality for its stated purpose.