Vision QA MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_MODEL | No | Optional. The model to use for QA (default: claude-opus-4-8). Can be set to claude-haiku-4-5 or claude-sonnet-4-6 for cost savings. | claude-opus-4-8 |
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key required for using Claude vision. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qa_checkA | Run a quality-control check on a generated image and return a structured verdict. Call this immediately after generating an image, before showing it to the user. Parameters:
Returns a dict with: passed (bool), overall_score, character_accuracy, style_consistency, quality_score, composition_score (all 0-1), issues (list of {severity, category, description, recommendation}), should_regenerate (bool), notes, and model. |
| list_scene_typesA | List the supported scene_type values and what each one expects. |
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
The two tools have completely distinct purposes: one lists scene types and their expectations, the other performs a quality check on images. There is no overlap or ambiguity.
Both tools use snake_case, but one follows a verb_noun pattern (list_scene_types) while the other uses an abbreviated prefix (qa_check). The pattern is mostly consistent but has a minor deviation.
With only 2 tools, the server is very focused. While it covers its core purpose, the count is on the low end and may feel thin for some use cases.
The tool set provides the essential functions: listing scene types and running a QA check. However, there is no tool to inspect or manage scene types beyond listing, and no tool to modify thresholds or references, leaving minor gaps.