Civo MCP by usefulapi

Each tool targets a distinct resource+action combination, and resource boundaries that could overlap (list_dns_domains vs list_dns_records, list_firewalls vs list_firewall_rules) are clearly differentiated by scope. Lifecycle tools (start/stop/reboot/set_tags) are unambiguously separate operations. An agent can reliably select the right tool.

Every tool follows the same civo_verb_noun convention (civo_list_instances, civo_get_instance, civo_create_dns_record, civo_reboot_instance). Verb choice is predictable and consistent across list/get/create/mutate operations. No camelCase mixing or vague verbs.

22 tools is on the heavier side but justified by the breadth of the Civo surface (instances, Kubernetes, databases, networks, volumes, firewalls, DNS, load balancers, billing). Each tool earns its place with no obvious redundancy, though it sits just above the comfortable range.

The surface is heavily read-oriented: it can list/get nearly everything but only create DNS records and firewall rules, with no create/delete for instances, clusters, networks, volumes, or databases. Instance lifecycle is covered (start/stop/reboot) but the absence of provisioning and delete operations leaves significant gaps for a cloud management server.