No user-submitted related servers found.
Scored across 33 tools
The set layers list/get/investigate/performance tools for the same resources (VMs, hosts, datastores, clusters), so overlap exists, but descriptions explicitly route agents between them (e.g., list_virtual_machines to resolve a name, get_vm_info for config, investigate_vm for a correlated bundle). Most selections are clear, though a few depth-based choices remain easy to confuse.
All names use snake_case verb_noun patterns with consistent prefixes: list_ for collections, get_ for details/metrics, investigate_ for correlated drill-downs, find_/scan_ for sweeps. Minor variance like list_all_clusters vs list_virtual_machines does not break the predictable convention.
33 read-only tools is well above the practical 3–15 range and past the 25+ 'too many' threshold, creating significant selection overhead even for a broad vSphere monitoring domain. Each tool has a narrow niche, but the volume is heavy for an agent-facing set.
Coverage spans clusters, hosts, VMs, datastores, networks, snapshots, performance, alarms, events, sensors, services, logs, certificates, licenses, capacity, tasks, sessions, and newer vLCM/tiering endpoints. Gaps remain for vSAN health, vCenter appliance certificate, datastore latency, and historical trending, though agents can often work around these via other servers or vCenter directly.