No user-submitted related servers found.
Scored across 38 tools
Most tools target a distinct resource+action (list/inspect/logs/stats per container, image, volume, network), so selection is generally clear. However there are real overlaps: restart_loop_rca vs container_restart_summary (both rank restart/exit-code), image_and_volume_bloat vs dangling_images/dangling_volumes/system_df, and overview vs system_info/system_version/system_df. Descriptions disambiguate most of these, but an agent could still hesitate between the aggregate and the granular tools.
There is a recognizable verb_noun convention (list_containers, inspect_image, start_container, prune_volumes, update_container), but a large minority of tools are noun-first or noun-phrase (container_logs, container_stats, container_top, system_info, system_df, stack_detail, image_disk_usage, resource_pressure_analysis, restart_loop_rca, dangling_images). The mix is readable but not predictable enough for a clean 4.
38 tools is on the heavy side (25+ is flagged as too many), and the surface spans containers, images, volumes, networks, pods, endpoints, stacks, system, undo, and several RCA analyzers. Each tool does map to something concrete, but the aggregate tools (overview, image_and_volume_bloat, restart_loop_rca) duplicate granular ones, so a few could be merged.
Coverage is strong for an AIOps/remediation server: full read+lifecycle over containers (list/inspect/logs/stats/top/start/stop/restart/remove/update), images, volumes, networks, pods, endpoints, stacks, system, plus undo and RCA analyses. Gaps exist (no container exec/create, no image pull/build, no volume/network create), but these may be intentionally out of scope for host triage.