No user-submitted related servers found.
Scored across 42 tools
Most tools are clearly partitioned by platform prefix (prtg_*, zabbix_*) or by distinct SolarWinds resources, and descriptions are precise about what each returns. However, a few boundaries blur: active_alerts (cross-platform, deduped), zabbix_problems, and prtg_alarms all surface 'current problems', and schedule_maintenance (SolarWinds) vs schedule_maintenance_prtg vs zabbix_create_maintenance could be misselected at a glance.
PRTG and Zabbix tools follow a clean prefix_noun pattern, but the SolarWinds set mixes verb-first (list_events, mute_alerts, remove_node) and noun-first (node_status, interface_status, topn, noc_rollup) styles with no platform prefix. Singular/plural also varies (node_status vs nodes_list), so the set is readable but not consistent.
42 tools is heavy and above the 25-tool threshold, but the surface genuinely spans three separate monitoring platforms plus a write/undo governance layer, so the size is defensible rather than padded. It sits at the borderline end of manageable for an agent's working set.
Coverage is strong across read inventory, alerts, maintenance windows, mute/unmute, unmanage/remanage, node deletion, canned/raw SWQL, and an undo system, with acknowledge spanning all three platforms. Minor gaps remain (e.g. no explicit PRTG/Zabbix resource-deletion symmetry), but core lifecycle operations are present.