No user-submitted related servers found.
Scored across 52 tools
Each tool targets a distinct resource and action pair: bulk calls, phone numbers, agents, providers, and knowledge files are clearly separated. Even close tools like listLLMProviders vs listSTTProviders vs listTTSProviders vs listAllProviders are differentiated by their explicit service scope. No two tools appear to be duplicates.
The vast majority of tools follow a predictable camelCase verb + noun pattern (createAgent, listPhoneNumbers, deleteKnowledgeBaseFile). Minor deviations exist such as bulkCallActions, which is a noun-style name rather than a verb + noun, and fetchBulkCalls vs the more common list* verb family. Overall naming is consistent and readable.
With 52 tools, this is a very large surface area, well above the 25+ threshold for a 'too many' rating. Although the domains are logically grouped, the sheer number makes it harder for agents to scan and select, and some bulk-control tools could arguably be consolidated into fewer—though still functional—endpoints.
The tool surface covers full CRUD lifecycles for agents, agent versions, phone numbers, knowledge-base files, and bulk-call campaigns, plus call logs and provider listing. Minor gaps exist, such as no explicit end-session or session retrieval beyond creation, and no file-content retrieval for knowledge-base files, but there are no dead-end workflows that would stop an agent.