A multi-agent e-commerce shopping assistant that finds products, compares prices, and analyzes reviews using real-time scraped data. Orchestrates remote A2A agents for price tracking, product recommendation, and review analysis.
This server exposes only 2 tools with minimal schema definition and poor descriptions. Tool names lack action verbs (amazon_scraper, google_search are acceptable but generic). Descriptions are extremely brief (10-15 chars each), well below the 50-200 char baseline for LLM-optimized tools. Input schemas are present but minimal: only a single 'input_str' parameter with basic string type, no enums, no validation constraints, no output schema documentation. No error handling guidance, no parameter dependencies documented, no pagination support despite tools returning lists. The server is built on A2A (Google's Agent API), not MCP, it does not register tools via MCP protocol at all. Tool definitions are inferred from agent skill metadata, not explicit MCP tool registration.
Fetch price of the first Amazon product.
Search the internet using Google Search to find product recommendations and reviews.
Tool descriptions are critically short (10-15 chars). 'Fetch price of the first Amazon product' and 'Search the internet using Google Search...' lack context for LLM selection. Baseline is 50-200 chars; these are 1/5 the minimum.
Input schemas are minimal. Both tools accept only 'input_str' (string type). No enums, no format constraints, no validation rules, no min/max length. LLMs cannot infer valid input ranges or formats.
No output schemas documented. LLMs do not know what fields to expect from amazon_scraper or google_search results. Cannot plan downstream tool calls or extract structured data.
Server is built on A2A (Google Agent API), not MCP. Tools are registered as AgentSkill objects in A2A, not via MCP protocol. This is a fundamental architecture mismatch, the server cannot be used as an MCP server by MCP clients.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 26 | <=2025-11-25 | v2 |
No error handling guidance. If amazon_scraper fails to find a product or google_search times out, there is no recovery hint for the LLM. No categorization of retryable vs fatal errors.