MCP server for managing backorder reservations and queue positions in e-commerce inventory systems
This server has critical gaps across all definition quality dimensions. The single tool 'reserve_backorder' lacks proper MCP structure, has minimal descriptions, and no evidence of being registered as an MCP tool. The source code shows a basic Python class with one method, but no MCP server framework, tool registration mechanism, or protocol implementation. The tool description is present but vague, parameters lack detailed descriptions, and there is no documented output schema. No error handling, validation, or security patterns are evident.
Reserve a backorder for a product SKU with specified quantity, returning queue position and estimated availability date
Tool description is under 50 characters and lacks WHEN/WHY context
Input parameters lack descriptions (sku, quantity, current_queue_len are named but not explained)
Output schema is not documented; response structure is inferred from code only
No error handling or recovery guidance; no validation of inputs
Hardcoded 14-day assumption in tool logic; no configurability or parameter for restock delay
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 33 | 2026-07-28+ | v2 |
Tool accepts current_queue_len as input but does not validate it is non-negative
No idempotency hints or indication that repeated calls with same input are safe