No user-submitted related servers found.
Scored across 55 tools
Each tool targets a distinct resource + action (job_list vs job_get vs delete_job, scale_deployment vs rollout_restart_deployment vs set_deployment_image vs rollout_undo_deployment). The few adjacent diagnostic tools (pod_describe, pod_health_rca, workload_readiness_rca, event_list) are explicitly scoped in their descriptions, so misselection risk is low.
Strong, predictable snake_case resource_action pattern (job_list, pod_get, delete_namespace, scale_statefulset, cordon_node), with a few deviations like cluster_info, api_resources, and the *_rca scan tools that follow a noun/concept rather than verb_noun convention. Readable and mostly uniform throughout.
55 tools is well above the 3-15 sweet spot and past the 25+ 'too many' threshold. Kubernetes is broad enough that most individual tools earn their place (list/get pairs per resource), but the surface is heavy and forces an agent to sift through many similar read endpoints to find the right one.
Read/list/get coverage is broad across pods, workloads, nodes, network, storage, RBAC-adjacent, diagnostics, and metrics, plus key remediations (scale, rollout, set image, cordon/drain, namespace lifecycle) and a thoughtful undo system. Gaps remain: no exec/port-forward, no create/update for deployments/services/configmaps/secrets/jobs, and no service_get detail, so some lifecycle operations lack coverage.
