Mob (Demo)

Most tools map to a clear resource+action pair, and overlapping queries like contact_get vs contact_timeline are differentiated by detail vs chronological progression. Some ambiguity remains where *_manage tools include list/get actions (e.g., debt_manage, tag_manage) while other resources have separate *_list tools, but descriptions mostly resolve this.

The dominant convention is resource_verb (contact_create, gift_list, activity_manage), but this is uneven: manage_push_notifications and manage_settings invert the order, batch_* uses an adverb prefix, and prime, upcoming_birthdays, and contacts_needing_attention don't follow the pattern. Names are readable but not predictable enough for an agent to guess a tool name reliably.

42 tools is a very heavy surface for a single MCP server, even for a broad CRM demo. While action parameters consolidate many CRUD operations, there are still borderline-redundant utilities (contact_get vs contact_timeline, contacts_needing_attention vs contact_list) that could be merged or removed.

The tool set covers CRUD plus specialized operations for nearly every CRM entity: contacts, activities, notes, reminders, tasks, gifts, debts, life events, and relationships, with batch creation, search, export, and statistics. Minor gaps exist (no bulk update/delete, no separate company object), but agents can complete realistic workflows without dead ends.