No user-submitted related servers found.
Scored across 11 tools
Most tools occupy clearly separated niches: ebms_get vs ebms_export is explicitly split by size/side-effects, ebms_write is the sole mutator while po_from_csv/batches_from_csv/import_from_csv are read-only drafters, and mrp_plan vs mrp_item_view split company-wide planning from a single BOM tree. The remaining fuzziness is among the three '*_from_csv' drafters (worksheet BUY rows, MAKE rows, arbitrary entity files), which an agent must read carefully to pick correctly, and ebms_get vs ebms_export overlap in a grey zone of 'a few hundred rows'.
All names are lower snake_case and cluster into readable prefixes (ebms_*, mrp_*, *_from_csv), so the set is predictable. It is not a single uniform verb_noun pattern though: ebms_get/ebms_write/ebms_export are prefix+verb, while po_from_csv/batches_from_csv/import_from_csv use a source-oriented noun_from_source form, and mrp_item_view adds a third shape.
Eleven tools is well inside the healthy range and each one earns its place: read, write, bulk export, plan, per-item view, three drafters for distinct sources, command, guide and company listing. No obvious filler or overlapping convenience wrappers.
The surface covers the full lifecycle: discovery (ebms_companies, ebms_guide), read/aggregate (ebms_get, ebms_export), mutation (ebms_write, ebms_command), planning (mrp_plan, mrp_item_view) and bulk intake (three drafters). The main gap is introspection — there is no tool to list entity metadata/fields or allowed commands directly, so an agent must go through ebms_guide's reference files to learn valid paths and the command allow-list.