The Groceries MCP server has significant definition quality issues. Tool naming is adequate (verb-noun pattern), but descriptions are extremely brief and lack the specificity needed for LLM decision-making. Parameter schemas are present but minimal, types are declared but descriptions are generic. Most critically: duplicate tool definitions (three identical 'search' tools), missing output schema documentation, no error handling guidance, and inadequate parameter descriptions. The server exposes write operations (add/remove cart items, user authorization) with minimal constraints or confirmation patterns. Schemas lack validation metadata (ranges, enums, constraints). This represents a typical community server with functional but low-quality definitions.

• Consolidate the three 'search' tools into one, or rename them clearly to indicate provider-specific variants (e.g., 'search_keshet', 'search_rami_levy') so the LLM knows which to call.
• Expand tool descriptions to 100-200 characters. For each tool, explain: (1) What does it do? (2) When should I call it? (3) What does it return? Example: 'add_items_to_cart: Adds groceries to your shopping basket. Call this after search() to add items you want to purchase. Returns the updated cart with totals.'
• Add parameter descriptions for 'items' array: 'Array of grocery items to add. Each item must have an id (from search results) and quantity (number, e.g., 2 for 2 units). Maximum 50 items per call.'
• Change 'quantity' parameter type from 'string' to 'number' and add constraints: 'quantity: {type: number, description: "Number of units to add (1-999, e.g., 2 for 2 bottles of milk)", minimum: 1, maximum: 999}'.
• Document output schema for search(): 'Returns {items: [{id: string, name: string, price: number, quantity_evaluation: object}], total: number}. Limit: 20 items per page.'
• Add error handling guidance: Describe how add_items_to_cart fails (e.g., 'If item out of stock, error: "Item {id} is out of stock. Try a similar product from search results." Recovery: search for alternatives.')
• Implement confirmation pattern for destructive operations: add a 'dry_run' parameter to cart operations, or return a preview before confirming the update.
• Clarify user_authorization: 'Tool to enable user-initiated OAuth or manual login flow. Call this if the user reports they are not authenticated. Returns success or a URL to complete authorization. No LLM-initiated authorization without explicit user consent.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry