No user-submitted related servers found.
Scored across 32 tools
Most tools map cleanly to a distinct resource+action (list_subnets/get_subnet, list_routers/get_router), so selection is usually obvious. The main friction is the overloaded 'services' family — list_services (Keystone catalog) vs list_compute_services, list_volume_services, and list_network_agents — plus list_volumes/list_volume_attachments/list_volume_services, which rely heavily on descriptions to tell apart.
Nearly everything follows a predictable snake_case verb_noun pattern with list_X/get_X pairs per resource, which makes the set easy to scan. get_scope is the one outlier: it does not retrieve a cloud resource by ID and breaks the otherwise uniform 'get one <resource>' semantic.
Thirty-two tools is heavy, but they are distributed across five OpenStack services (Nova, Neutron, Cinder, Keystone) in a mechanical list/get pattern rather than being redundant filler. It sits at the borderline where an agent must scan a large namespace to find the right call.
The surface is entirely read-only: there is no way to create, update, or delete a server, volume, network, or security group, nor any server action tools (start/stop/reboot) or volume attach/detach. For a server named openstack-mcp-server, the read path is thorough but the lifecycle coverage is a significant gap.