Related Servers

Multiple tool clusters have unclear boundaries: get_sales_analysis duplicates the fixed-dimension SMLSVC aggregators (get_top_customers, get_sales_by_period, get_warehouse_sales, etc.), four raw-query mechanisms (call_service_layer, query_sml_view, query_sql_direct, query_hana_direct) compete for the same 'fetch data' role, and five inventory tools (get_total_stock, check_atp, monitor_reorder_items, calc_reorder_point, predict_stockout) all answer 'do I need to reorder?'. Individual descriptions are clear, but an agent will frequently face several plausible tools for one question.

The set overwhelmingly follows a predictable snake_case verb_noun pattern (create_*, get_*, calc_*, detect_*, analyze_*, forecast_*), making the surface readable and routable. Minor deviations: create_po_from_quotation uses the 'po' abbreviation while its siblings use full 'purchase_order', and read operations mix get_, query_, list_, and call_ verbs.

At 65 tools this far exceeds the 16-25 'heavy' range, and the Order-to-Cash name describes only a fraction of the surface — the rest spans purchase-to-pay, inventory analytics, forecasting, financial reporting, and raw database access. While SAP B1 is a large system, an agent must navigate an enormous list where much of the analytics work could be consolidated behind fewer, more parameterized tools.

The forward document lifecycle is thoroughly covered for both sales (quotation→order→delivery→AR invoice→payment) and purchasing (request→RFQ→PO→GRPO→AP invoice→payment), with extensive read/query coverage. However, there are no update/cancel/close tools for documents, no credit-memo or returns creation, and reverse flow only exists as read-only query views — call_service_layer is the sole workaround for these gaps.