Model Context Protocol (MCP) server for Amazon marketplace data. Runs in demo-mode and returns synthetic data generated on the fly. In production, could be replaced with real data provider client (such as Keepa API client).
Server has 5 tools with consistent naming (verb_noun pattern: get_*) and valid input schemas. All tools accept ASIN with proper regex validation (^[A-Za-z0-9]{10}$). However, descriptions are minimal (15-25 chars), falling below the 50-200 char LLM-optimized baseline. No output schemas are documented in the source code. Parameter descriptions exist but are terse. No error handling guidance visible. Tools are read-only (good for safety) but lack context about when to use each tool vs. alternatives.
Check if the ASIN is restricted/gated and provide a reason.
Get the 90-day Best Seller Rank (BSR) history list for a given ASIN.
Get the referral fee percentage and FBA fulfillment fee for a given ASIN.
Get the 90-day price history list for a given ASIN.
Get basic product details (title, category, current price) for a given ASIN.
Tool descriptions are 15-25 characters, well below the 50-200 char LLM-optimized baseline. Descriptions lack context about WHEN to use each tool (e.g., when to call get_price_history vs get_bsr_history for arbitrage analysis).
No output schemas documented in source code. LLMs cannot infer what fields are returned (e.g., does get_product return price as float or string? What fields does get_fees return?). This forces agents to guess and wastes tokens on clarification.
No error handling guidance visible. If an ASIN is invalid or not found, what does the tool return? How should the agent recover? No recovery hints provided.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2025-06-18+ | v2 |
Parameter description for 'asin' is generic ('The 10-character Amazon Standard Identification Number'). Does not explain why ASIN is needed or what happens if it's invalid. No guidance on how to obtain an ASIN if the agent doesn't have one.
Tool composition unclear. Five separate get_* tools all take the same ASIN parameter. No guidance on which tools to call together for a complete arbitrage analysis, or whether a batch variant would be more efficient.