No user-submitted related servers found.
Scored across 14 tools
Tools are grouped into clear resource families (crm_*, call_*, *_status) and the three call placement tools are cleanly separated by medium (TTS, WAV, IVR app). The one soft boundary is crm_add_or_update (with overwrite) versus crm_set_field, since both can change an existing field value, but the descriptions largely disambiguate them.
Most tools follow a <group>_<object> pattern, and the crm_ family is consistently verb_noun (crm_get_field, crm_set_field, crm_add_note). However the call family flips ordering/noun-verb intent (call_status vs call_text/call_audio/call_ivr, plus campaign_status/import_status), so conventions are mixed though still readable.
14 tools sit comfortably in the well-scoped range and each maps to a distinct operation (field access, messaging, campaign/import monitoring, agent notifications). Nothing appears redundant or padding-like.
Core outbound actions and status checks are covered, but the surface has notable gaps: no CRM search or list (explicitly stated), no way to read more than one field at a time, no campaign creation/listing despite campaign_status, and DO_NOT_CALL/DO_NOT_EMAIL flags can be set but never cleared. Agents can work around some of these via record IDs, but discovery-heavy workflows will hit dead ends.
