No user-submitted related servers found.
Scored across 13 tools
Several pairs are functionally near-identical: find_stores vs list_apple_stores (both return stores for a country), and search_products vs browse_sitemap (both traverse the sitemap to discover product pages). The availability cluster (compare_availability, check_variant_pickup, check_delivery, check_configuration_delivery, get_configuration_pickup) has real pickup/delivery distinctions but enough overlap that an agent can easily pick the wrong one, especially between compare_availability and the individual check_* tools.
All names are snake_case verb_noun (get_product, check_delivery, browse_sitemap), which is a clear predictable pattern. Minor drift: 'list_apple_stores' injects the vendor name where the sibling uses plain 'find_stores', and verbs vary broadly (find/list/search/get/explore/check/compare/browse) for similar read operations.
13 tools sits comfortably in a well-scoped range for a read-only storefront/product/availability server. The count is slightly inflated by redundant store-listing and availability tools that could be consolidated into 2-3, but nothing feels gratuitous at a per-domain level.
The lifecycle is well covered for a read-only server: store discovery, storefront metadata, product search/detail, configuration options, and pickup/delivery estimates, with purchase explicitly out of scope. Minor gaps remain—no get_store for store details/hours by ID and no direct category or product-listing primitive beyond sitemap paging.