No user-submitted related servers found.
Scored across 42 tools
Tools are mostly distinct, with platform prefixes and separate resource names making selection clear. The main ambiguity is between pause_sensor/schedule_maintenance_prtg and mute_alerts/schedule_maintenance/unmanage_node, where similar suppression semantics overlap despite helpful descriptions.
All names are snake_case and readable, but no single convention is followed: reads mix noun-first names like nodes_list and zabbix_problems with verb-first names like list_events and list_unmanaged. Platform prefixes are also applied unevenly, such as pause_sensor being PRTG-specific while other PRTG tools use the prtg_ prefix.
At 42 tools this is well beyond the 25+ threshold and creates a heavy selection burden for agents. The three-platform scope justifies a larger surface, but it would be cleaner split into per-platform servers or consolidated further.
The set covers the core monitoring lifecycle: health reads, alerts, history, acknowledgements, pause/resume, maintenance windows, mute/unmute, unmanage/remanage, node removal, and SWQL for arbitrary SolarWinds queries. Minor gaps exist, such as no SolarWinds metric history wrapper and limited PRTG/Zabbix write operations, but these are workable via existing tools.