AgencyBloc MCP by usefulapi

Most tools map cleanly to one entity plus action, and get_* vs search_* tiers are clearly distinct. The main possible confusion is get_activities (retrieve by IDs) vs list_activities (list for one entity), but the descriptions make that boundary clear.

All tools use an agencybloc_ prefix followed by a predictable verb_noun pattern such as create_group, get_policy, search_agents, and update_individual. Minor variants like search_leads_by_phone remain readable and consistent with the overall convention.

Twenty-two tools is somewhat above the ideal 3–15 range, but AgencyBloc covers several distinct resources, and each tool corresponds to a useful operation. The set is slightly heavy rather than excessive for the domain.

Core groups, individuals, and policies have create/get/search/update coverage, and activities/notes support create and read with documented API limitations. However, agents lack create/update, carriers only have search, and leads only support get and phone search, leaving notable lifecycle gaps.