No user-submitted related servers found.
Scored across 19 tools
Each entity gets a clean search/get/aggregate triad with clearly different semantics (filtered multi-result, single fetch by id, grouped counts). Traversals are distinctly named per link (traverse_customer_orders, traverse_order_products, traverse_order_notes), and the write actions (add_order_note, assign_order, cancel_order) plus read_audit_log have no overlap with the read tools.
Strict verb_noun snake_case throughout: search_/get_/aggregate_ prefixes repeat identically across all four entities, traverse_ is used uniformly for link walks, and write/administrative tools follow the same lowercase verb_noun form. No mixing of conventions.
19 tools is on the higher side but each earns its place: a symmetric read/aggregate surface over four entities, three graph traversals, and three gated writes plus an audit reader. Nothing feels redundant, though the count sits at the upper boundary of comfortable.
Read coverage is complete and symmetric (search/get/aggregate for Customer, Order, Product, Note) with traversals across the main links and order lifecycle writes (assign, cancel, add note) plus auditing. Gaps are minor and arguably intentional: no create/update/delete for the mirrored entities, and no direct note-creation beyond add_order_note.