No user-submitted related servers found.
Scored across 37 tools
Every tool targets a distinct resource and action. Reads vs writes are clearly separated, and even similar-looking tools (device_status vs org_device_statuses, uplink_loss_and_latency_rca vs network_health_score) serve distinct purposes (single-device vs org-wide rollup, uplink-specific vs composite fleet score). No two tools overlap.
Naming is readable but mixed: some tools follow verb_noun (update_device, reboot_device, claim_devices_into_network) while others are noun_verb or noun-only (device_status, org_get, network_alerts, org_device_statuses, config_template_drift). Many start with the resource name, but the verb placement and format vary (get vs list vs status vs nouns like uplinks/ssids). This is not chaotic, but it lacks a single consistent convention.
At 37 tools, the server is heavily overloaded. The scope spans two platforms (Meraki and ACI) plus undo management, but even accounting for that, this far exceeds the typical well-scoped range (3-15). The count feels heavy and likely includes many narrow read-only tools that could be consolidated.
The surface covers extensive reads for Meraki (org, networks, devices, clients, traffic, health) and ACI (endpoint, EPG, faults), and some writes (device update/reboot, VLAN update, claim/remove, bind/unbind). But it lacks major operations: no network create/delete, no SSID or switch-port configuration, no ACI writes at all, and no org admin/licensing changes. These gaps will force agents to fail or improvise for common workflows.