No user-submitted related servers found.
Scored across 32 tools
Most tools target a clearly distinct resource and action, and the descriptions explicitly cross-reference when to use a bundle versus a raw list or health rollup. The three investigation bundles and the cluster-health/cross-vcenter/get_alarms family still create some functional overlap, so a few selections could be ambiguous for an agent.
The set consistently uses snake_case with recognizable list_/get_ prefixes and meaningful suffixes like _bundle, _status, and _performance. However, many names are noun phrases without a verb (license_status, active_tasks, vm_info), so the verb_noun pattern is not fully uniform.
At 32 tools, the set is well beyond the 25-tool threshold and feels heavy for an agent to navigate, even for a broad monitoring scope. The three investigation bundles largely duplicate combinations of the individual list/get/performance tools, inflating the count without adding fundamentally new data.
The read-only domain is broadly covered: inventory, live performance, health rollups, alarms/events, logs, capacity, snapshots, backup history, licensing, NTP, certificates, sessions/tasks, and patch compliance. Minor gaps remain—no historical trending, no datastore latency, and shallow network detail—but none create dead ends for the stated purpose.