view-image-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| view_imageA | Display an image file inline in the terminal using Kitty graphics protocol (Ghostty/Kitty). The image appears directly in the user's terminal. |
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 confusion or overlap between tools. The tool 'view_image' has a single, clearly defined purpose.
The single tool name 'view_image' follows a clear verb_noun pattern, and with only one tool, consistency is inherently perfect.
A single tool is too few for most server purposes, as it limits functionality and flexibility. For an image viewing server, this feels thin and under-scoped.
The server's domain appears to be image viewing, but with only a display tool, there are significant gaps such as listing images, resizing, converting formats, or handling metadata, which agents might need for full workflows.