Scored across 57 tools
Most tools target distinct resources with clear CRUD separation, but several pairs overlap in purpose: list_text_messages vs list_sms_threads, call_summary vs call_stats, and get_sms_thread vs get_text_message. The descriptions carefully explain the differences, so a careful agent can disambiguate, but the boundaries are not self-evident from tool names alone.
The CRUD tools follow a consistent list_/get_/create_/update_/delete_ pattern, but analytics and utility tools break it with noun-style names (call_summary, call_stats, usage_summary, form_stats, spam_detector) and non-standard verb forms (search_calls_by_number, bulk_update_calls, add_call_tags, remove_call_tags). The mixed conventions remain readable but lack a single predictable pattern.
With 57 tools, this server is well beyond the 'too many' threshold and into the extreme range. Even for a broad API, the surface is overwhelming and includes many granular variants (four summary/stats tools, three SMS-listing tools, and seven tag-related tools) that could be consolidated.
Coverage is broad across companies, trackers, calls, forms, SMS threads, tags, users, notifications, leads, and analytics. However, there are notable gaps: create_text_message is referenced in list_text_messages but does not exist as a tool, form submissions have no delete operation, and account-level get/update is missing. Agents can work around most gaps but may hit dead ends.