No user-submitted related servers found.
Scored across 45 tools
Several tools share overlapping domains, such as sales campaigns v1 vs v2, retail sales wrappers vs raw mpobracun, stock status variants (regular, supplier, serial), and multiple order types, which can cause misselection. However, descriptions often clarify use cases and explicitly state preferences (e.g., 'PREFERRED for last N sales orders'), mitigating some confusion.
All tools use a consistent luceed_ prefix and snake_case, making names predictable. However, the set mixes resource-name tools (luceed_artikli, luceed_partneri) with convenience/action tools (luceed_retail_sales_summary, luceed_recent_sales_orders, luceed_get) rather than a uniform verb_noun pattern.
With 45 tools, the set is heavy for an agent to manage, and several tools could be consolidated (sales campaign versions, retail sales wrappers, stock status variants). While the ERP domain is broad, the volume risks overwhelming agents and increases selection difficulty.
For a read-only ERP integration, the surface covers most major resources (products, stock, prices, partners, orders, invoices, CRM, hotel) and includes luceed_get and luceed_catalog for ad-hoc gaps. Write operations are largely absent, but this appears intentional for the read-only scope.