Aircall MCP by usefulapi

Each tool targets a distinct resource and action combination (get_call vs get_call_summary vs get_call_transcription are clearly delineated by their subject). The only mild overlap is list_calls vs search_calls, but descriptions distinguish filtered listing from free-text search. No two tools would be easily confused.

Every tool follows the identical aircall_verb_noun pattern (aircall_get_call, aircall_list_users, aircall_create_contact, aircall_search_contacts). The verb vocabulary is consistent (get/list/search/create/update/add/tag) and resource nouns are singular/plural used predictably.

25 tools is on the heavy side for the stated scope, but each appears to map to a distinct REST endpoint across six resource families (calls, contacts, numbers, tags, teams, users) plus AI call features. The set is broad but not padded with redundant tools, so it is defensible though somewhat bulky.

Calls and contacts are fairly well covered (list/get/search/create/update plus tagging and comments), but there is no delete_contact, no delete/update for calls, and no write operations at all for numbers, tags, teams, or users. Notable lifecycle gaps exist, though the core read and contact-creation workflows are usable.