No user-submitted related servers found.
Scored across 65 tools
Most tools target a distinct tool/resource (kube vs helm vs argo vs tf vs per-language lint/test), but several pairs are near-neighbors: find_files vs glob, git_diff vs git_diff_content, tf_state_list vs tf_show, and the cluster of '*_health_summary'/'*_failure_summary'/'*_diagnose' triage tools overlap conceptually with the plain getters they wrap. Descriptions do resolve most of these, but at 65 tools an agent must read carefully to avoid picking e.g. kube_get over kube_diagnose_pod when a diagnosis is wanted.
Everything is snake_case, which is good, but the prefix/verb ordering is mixed: domain-prefixed noun-first (git_status, kube_get, tf_plan_summary, argo_app_diff) coexists with verb-first (list_guidance, check_environment, result_get) and bare Unix-style names (ls, tree, du, rg, glob, cat, jq, yq, run, batch). Readable, but not a single predictable pattern.
65 tools is very heavy, even for a broad shell/devops toolbox spanning git, k8s, Terraform, ArgoCD, Helm, four language toolchains, and CI. Each tool is defensible in isolation, but the surface invites selection errors and could be consolidated (e.g. per-language lint/typecheck/test trios, summary vs getter variants).
Read/inspect coverage is deep across every advertised domain (files, git, Terraform, k8s, ArgoCD, Helm, CI, language toolchains), and run/batch act as an escape hatch for anything missing. Gaps are mostly write-side: no git mutations (commit/checkout/push), no kube apply/scale/exec, no file edit—though run largely works around them.