MCP server for OpenAI image generation
Server has 3 tools with schemas and descriptions, but quality is inconsistent. oai_generate_image has comprehensive schema with proper enums and constraints (prompt max 32000 chars, n 1-10, output_format enum). However, descriptions are generic and lack LLM-optimized guidance on WHEN to use each tool or what happens on failure. health_check and simple_generate_image lack depth. No error handling guidance, no recovery patterns, no output schema documentation. Parameters are well-typed but descriptions don't explain dependencies or constraints in natural language. Missing: pagination, output structure docs, idempotency guidance, and actionable error messages.
Health check endpoint for the MCP server
Generate images using OpenAI's image generation API
Simplified image generation tool that only requires a prompt
Tool descriptions lack LLM-optimized guidance. 'Generate images using OpenAI's image generation API' is generic and doesn't explain WHEN to use oai_generate_image vs simple_generate_image, what happens on API failure, or what the output contains.
No output schema documented. Tools return image data but LLM cannot infer structure (URLs? base64? file paths?). Baseline: 100% of A+ tools document return types.
No error handling guidance. Code catches errors but returns generic messages. LLM cannot determine if error is retryable, user-fixable, or fatal. Missing recovery patterns like 'If API rate-limited, wait 60s and retry'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
health_check description is 24 chars ('Health check endpoint for the MCP server'), below 20-char floor.
Parameter descriptions in oai_generate_image repeat enum values instead of explaining intent. E.g., 'Must be one of transparent, opaque or auto', better: 'Controls background transparency. Use transparent for PNG with alpha channel, opaque for solid backgrounds, auto for API default.'