Sortly MCP by usefulapi

Most tools target clearly distinct resource+action pairs, and the three item reads (list_items, list_recently_updated_items, search_items) are differentiated by their descriptions (full listing, incremental sync, name search). The only mild overlap is sortly_move_item versus sortly_update_item with parent_id for folder relocation, but the descriptions explicitly clarify the split.

Every tool follows the identical sortly_verb_noun snake_case pattern (sortly_create_item, sortly_get_job, sortly_list_purchase_orders, sortly_move_item). Verbs are consistent across the set and the naming makes scoping and intent immediately predictable.

20 tools for a multi-resource inventory system (items, folders, jobs, purchase orders, alerts, custom fields, units) is reasonable and each tool maps to a real operation. It is on the heavier side of the sweet spot, but nothing feels redundant.

Coverage is strong on create/get/list for items, jobs and purchase orders, but there are notable gaps: no delete tools anywhere, no update for jobs or purchase orders, and a receive-status reader without a corresponding tool to actually trigger a PO receive. Alerts and custom fields are read-only beyond creation, leaving several lifecycle dead ends.