Simple MCP server to add images to Cloudflare Images
Single tool with adequate naming and schema, but critical gaps in parameter descriptions and output documentation. Tool name 'add_image_to_cloudflare_images' follows verb_noun convention and is clear. Input schema is present with types (string, object), but the 'metadata' parameter lacks actionable constraints. No output schema is documented, LLMs cannot predict the response structure. Error handling exists but lacks recovery guidance. Overall: functional but below production baseline.
Adds an image to Cloudflare Images from a URL or a local file path.
Output schema not documented. Tool returns TextContent with JSON-serialized Cloudflare API response, but LLMs cannot predict field names, types, or structure. Downstream tools cannot reliably extract image_id or other references.
Metadata parameter lacks constraints. Described as 'object' with no type hints, format, or valid key/value examples. LLMs will guess at structure, risking API rejection.
Error messages lack recovery guidance. HTTPStatusError returns raw API response text; LLMs cannot determine if error is retryable, user-fixable, or fatal. No suggestion for next steps.
No idempotency guarantee documented. Tool modifies state (uploads image) but does not declare idempotent behavior. Agents retrying on transient failures risk duplicate uploads.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
Tool description does not state that operation is destructive/irreversible. LLMs need explicit signal that uploads cannot be undone without a separate delete call.