No user-submitted related servers found.
Scored across 17 tools
Most tools have clearly distinct purposes organized around a diagnosis→remediate→verify workflow (rank_suspects, get_blast_radius, recent_changes, trace_dependency_path), so misselection is unlikely. Minor overlap exists between verify_recovery and get_service_health (both report health) and between rank_suspects and explain_incident/find_similar_incidents (all surface past-incident context), but descriptions disambiguate well enough.
Nearly all names follow a predictable snake_case verb_noun pattern (get_owner, open_incident, resolve_incident, restart_service, verify_recovery). A couple of noun-only names (recent_changes) break the pattern slightly, but the convention is clear and readable throughout.
17 tools is slightly above the ideal band, but each covers a genuinely distinct operation across a broad incident-response domain (detection, diagnosis, remediation, communication, verification) and none feels redundant. The surface is well-scoped for the complexity of the purpose.
The set covers the full incident lifecycle: diagnosis (rank_suspects, blast radius, changes, paths, ownership), memory search (find_similar_incidents, explain_incident), incident management (open/notify/resolve), remediation (rollback, restart, feature flag), verification (verify_recovery, health, logs), plus a query_graph escape hatch. No obvious dead ends for the stated purpose.
