feat(kubevirt): add vm_troubleshoot tool for automated VM diagnostics

Adds a new `vm_troubleshoot` MCP Tool that collects comprehensive
diagnostic data for KubeVirt VirtualMachines including VM/VMI status,
DataVolume/PVC state, cloud-init configuration, virt-launcher pod state,
pod logs, and related events.

Key features:
- Targeted event collection using field selectors (no namespace-wide scan)
- DataVolume/PVC status with StorageClass identification
- Cloud-init extraction with sensitive field redaction (passwords, SSH keys)
- Only falls back to PVC lookup when DataVolume is genuinely NotFound

This tool enables AI assistants to proactively diagnose VM issues such as
missing StorageClasses, invalid PVC specs, misconfigured cloud-init, and
scheduling constraints without requiring the user to manually inspect
resources.

Complements the existing vm-troubleshoot Prompt with a proper Tool that
LLMs can invoke automatically based on user intent.

Signed-off-by: Shirly Radco <sradco@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

Author: sradco

pkg/mcp/testdata/toolsets-kubevirt-tools.json

@@ -233,5 +233,34 @@
     },
     "name": "vm_lifecycle",
     "title": "Virtual Machine: Lifecycle"
+  },
+  {
+    "annotations": {
+      "destructiveHint": false,
+      "idempotentHint": true,
+      "openWorldHint": true,
+      "readOnlyHint": true,
+      "title": "Virtual Machine: Troubleshoot"
+    },
+    "description": "Diagnose KubeVirt VirtualMachine issues by collecting VM status, VMI status, volumes, DataVolume/PVC state, cloud-init configuration, virt-launcher pod state, pod logs, and related events. Returns a structured diagnostic report with root-cause data that goes beyond what alerts provide. Use this tool FIRST whenever a user asks why a VM is not starting, stuck in Provisioning, crashlooping, failing to migrate, or exhibiting unexpected behavior. Identifies issues such as missing StorageClasses, invalid PVC specs, misconfigured cloud-init, and scheduling constraints.",
+    "inputSchema": {
+      "properties": {
+        "name": {
+          "description": "The name of the VirtualMachine to troubleshoot",
+          "type": "string"
+        },
+        "namespace": {
+          "description": "The namespace of the VirtualMachine to troubleshoot",
+          "type": "string"
+        }
+      },
+      "required": [
+        "namespace",
+        "name"
+      ],
+      "type": "object"
+    },
+    "name": "vm_troubleshoot",
+    "title": "Virtual Machine: Troubleshoot"
   }
 ]

pkg/toolsets/kubevirt/toolset.go

@@ -10,6 +10,7 @@ import (
 	vm_create "github.com/containers/kubernetes-mcp-server/pkg/toolsets/kubevirt/vm/create"
 	vm_guestagent "github.com/containers/kubernetes-mcp-server/pkg/toolsets/kubevirt/vm/guestagent"
 	vm_lifecycle "github.com/containers/kubernetes-mcp-server/pkg/toolsets/kubevirt/vm/lifecycle"
+	vm_troubleshoot "github.com/containers/kubernetes-mcp-server/pkg/toolsets/kubevirt/vm/troubleshoot"
 )
 
 type Toolset struct{}
@@ -30,6 +31,7 @@ func (t *Toolset) GetTools(_ api.Openshift) []api.ServerTool {
 		vm_create.Tools(),
 		vm_guestagent.Tools(),
 		vm_lifecycle.Tools(),
+		vm_troubleshoot.Tools(),
 	)
 }