No user-submitted related servers found.
Scored across 46 tools
Most tools target a distinct resource+action, and descriptions go to great lengths to say when to use one over another (e.g. get_alert vs investigate_alert, get_capacity_overview vs get_remaining_capacity vs get_time_remaining). There are genuine near-neighbors — get_resource / get_resource_health / get_resource_riskbadge / get_resource_properties, and the three capacity tools — but each is explicitly differentiated in text, so misselection is mitigated rather than likely.
Strong, predictable verb_noun snake_case across the surface: list_alerts, get_alert, create_alert_definition, delete_alert_definition, list_fleet_certificates, start_resource_maintenance. Minor deviations exist (promql_query is a bare noun, search_api_operations/get_api_path are slightly odd but readable), so it is not perfectly uniform.
46 tools is a heavy surface for an operations/monitoring server, spanning alerts, capacity, resources, maintenance, reports, fleet, health and collectors. Many are individually justifiable, but the volume makes discovery and selection expensive and pushes past the well-scoped 3-15 range.
Coverage is broad and lifecycle-aware: alerts (list/get/acknowledge/cancel/notes/recommendations), definitions (create/list/set state/delete), symptoms, capacity, resources/metrics/properties/relationships, maintenance, reports, fleet and platform health. Gaps remain — no read/update for a single alert definition, no symptom-definition creation, no resource write operations — but most core workflows are closed.