Vision MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_MODEL | Yes | Model name for vision tasks | |
| OPENAI_API_KEY | Yes | API key for authentication | |
| OPENAI_API_BASE | Yes | API base URL |
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 |
|---|---|
| analyze_imageA | |
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 'analyze_image' has a singular, clearly defined purpose of analyzing image content, making disambiguation perfect.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'analyze_image' follows a clear verb_noun pattern, which would be consistent if more tools were added.
A single tool for a 'Vision MCP' server feels thin and incomplete for the apparent scope of image analysis. While the tool is powerful, the domain likely requires more operations (e.g., image processing, comparison, or metadata extraction) to be well-scoped, making the count too low.
The tool surface is severely incomplete for a vision-related domain. It only provides analysis, with no support for other common operations like image generation, editing, filtering, or batch processing. This will cause agent failures when tasks require more than basic analysis.