No user-submitted related servers found.
Scored across 28 tools
Several clusters overlap meaningfully: foran_track_order vs foran_order_status vs foran_order_details all return order status/contents, and the generic search/fetch duplicate foran_search_products/foran_product_details with a different id scheme. foran_cart_remove vs foran_cart_update (quantity 0 removes) and foran_about vs foran_policy (which includes an 'about' topic) vs foran_buying_guide also blur together. Descriptions do give hints (guest vs logged-in, all-areas vs near-customer), so an agent can usually recover, but misselection is likely.
Most tools follow foran_<verb>_<noun> (foran_cart_add, foran_place_order, foran_track_order), but the set mixes noun-only names (foran_wallet, foran_coupons, foran_about, foran_policy), a 'my_' family (foran_my_account, foran_my_orders, foran_my_addresses), and two bare verbs (search, fetch) with no server prefix. Similar functions use different conventions (foran_track_order vs foran_order_status), so the pattern is readable but not predictable.
28 tools is heavy and sits just above the range where an agent can scan the surface comfortably, though a delivery app domain (cart, catalogue, orders, account, policies, staff) legitimately needs many operations. Some slots are redundant (search/fetch duplicating the foran_search_products / foran_product_details pair, and track_order/order_status), so trimming would help.
Coverage is broad: full cart CRUD, search/discovery, store and product details, checkout with confirmation, order listing, details, cancellation, tracking, wallet/coupons/account, staff and custom-order flows. The main gaps are address creation (explicitly punted to the app, a dead end for agents) and wallet top-up, neither of which blocks the core ordering lifecycle.