No user-submitted related servers found.
Scored across 7 tools
Each tool maps to a clear, distinct action: searching, viewing, adding, removing, clearing, reordering, and status checking. Even where add_item and reorder_from_history both add to the cart, their purposes are obviously different (single product vs. bulk from order history). check_status overlaps slightly with view_cart by reporting cart size, but its primary role is connection health, which is separate.
All tool names share the rami_levy_ prefix and follow the same verb_noun snake_case pattern: view_cart, search_products, add_item, remove_item, clear_cart, reorder_from_history, check_status. This makes the tool surface highly predictable and easy for an agent to navigate.
Seven tools is a well-scoped size for this server's purpose: search a catalog, manage a cart, reorder from history, and verify connectivity. Each tool earns its place with no obvious redundancy or bloat.
Core cart lifecycle is covered: search products, view cart, add, remove, clear, reorder, and check status. The main gap is that there is no way to adjust a product's quantity directly (only add-to-existing or remove the whole line), and order history is used internally by reorder_from_history but not exposed for viewing.