No user-submitted related servers found.
Scored across 60 tools
Most tools have clearly distinct purposes, but there is some overlap among stock reports (get_stock, get_stock_by_store, get_stock_current) and among search tools (search_products, search_assortment, search_variants). The descriptions help resolve ambiguity, but an agent might still struggle to pick the right one in edge cases.
The naming mostly follows a consistent verb_noun pattern (search_*, get_*, create_*, update_*, list_*, delete_*). However, there is a mix of 'get' and 'list' for collection endpoints (get_orders vs list_invoices_out), and some verbs are more specific than others (update_prices, update_customer_order_status). Overall, the pattern is readable and predictable.
With 60 tools, this is far beyond the 25+ threshold for 'too many'. Even for an ERP-like system like MoySklad, the sheer number makes the toolset unwieldy and difficult for an agent to navigate efficiently. The scope is broad, but the count is excessive.
The toolset covers a wide range of MoySklad operations, including products, orders, stock, payments, webhooks, and reports. However, there are notable gaps: many entities only have create and read but lack update and delete (e.g., products, counterparties, payments). The generic get_documents/get_document partially compensate, but the missing CRUD operations create dead ends.