No user-submitted related servers found.
Scored across 124 tools
Tool names largely map to distinct domains, and descriptions carefully distinguish similar operations (e.g. legacy vs new checkout orders, system_health vs stores_health). However, several near-duplicates exist: wafle_orders_list vs wafle_checkout_orders_list, wafle_orders_refund vs wafle_checkout_order_refund, wafle_abandoned_list vs wafle_checkout_cart_recover, plus explicit alias pairs for store settings. These are documented but could still cause misselection.
Almost all tools follow a consistent `wafle_<domain>_<resource>_<action>` snake_case pattern (products_list, coupons_update, agents_run). Minor deviations like wafle_users_me, wafle_auth_me, and wafle_ai_usage are predictable and do not seriously undermine the overall convention.
124 tools is far beyond the well-scoped range and creates significant agent tool-selection overhead. Even for a broad e-commerce platform, this is excessive and many endpoints could be consolidated or grouped behind sub-resources.
The platform covers the core e-commerce lifecycle extensively: stores, products, orders, coupons, customers, gateways, pricing, shipping, domains, ads, analytics, AI jobs, and agents. Notable gaps include product deletion, domain removal/detach, and some update operations, but most workflows have no dead ends.