feat: add cluster health check prompt

Signed-off-by: Rohit Patil <[email protected]>

Author: ropatil010

docs/PROMPTS.md

@@ -0,0 +1,99 @@
+# MCP Prompts Support
+
+The Kubernetes MCP Server supports [MCP Prompts](https://modelcontextprotocol.io/docs/concepts/prompts), which provide pre-defined workflow templates and guidance to AI assistants.
+
+## What are MCP Prompts?
+
+MCP Prompts are pre-defined templates that guide AI assistants through specific workflows. They combine:
+- **Structured guidance**: Step-by-step instructions for common tasks
+- **Parameterization**: Arguments that customize the prompt for specific contexts
+- **Conversation templates**: Pre-formatted messages that guide the interaction
+
+## Creating Custom Prompts
+
+Define custom prompts in your `config.toml` file - no code changes or recompilation needed!
+
+### Example
+
+```toml
+[[prompts]]
+name = "check-pod-logs"
+title = "Check Pod Logs"
+description = "Quick way to check pod logs"
+
+[[prompts.arguments]]
+name = "pod_name"
+description = "Name of the pod"
+required = true
+
+[[prompts.arguments]]
+name = "namespace"
+description = "Namespace of the pod"
+required = false
+
+[[prompts.messages]]
+role = "user"
+content = "Show me the logs for pod {{pod_name}} in {{namespace}}"
+
+[[prompts.messages]]
+role = "assistant"
+content = "I'll retrieve and analyze the logs for you."
+```
+
+## Configuration Reference
+
+### Prompt Fields
+- **name** (required): Unique identifier for the prompt
+- **title** (optional): Human-readable display name
+- **description** (required): Brief explanation of what the prompt does
+- **arguments** (optional): List of parameters the prompt accepts
+- **messages** (required): Conversation template with role/content pairs
+
+### Argument Fields
+- **name** (required): Argument identifier
+- **description** (optional): Explanation of the argument's purpose
+- **required** (optional): Whether the argument must be provided (default: false)
+
+### Argument Substitution
+Use `{{argument_name}}` placeholders in message content. The template engine replaces these with actual values when the prompt is called.
+
+## Built-in Prompts
+
+The Kubernetes MCP Server includes several built-in prompts that are always available:
+
+### `cluster-health-check`
+
+Performs a comprehensive health assessment of your Kubernetes or OpenShift cluster.
+
+**Arguments:**
+- `namespace` (optional): Limit the health check to a specific namespace. Default: all namespaces.
+- `verbose` (optional): Enable detailed resource-level information. Values: `true` or `false`. Default: `false`.
+- `check_events` (optional): Include recent warning/error events in the analysis. Values: `true` or `false`. Default: `true`.
+
+**What it checks:**
+- **Nodes**: Status and conditions (Ready, MemoryPressure, DiskPressure, etc.)
+- **Cluster Operators** (OpenShift only): Available and degraded status
+- **Pods**: Phase, container statuses, restart counts, and common issues (CrashLoopBackOff, ImagePullBackOff, etc.)
+- **Workload Controllers**: Deployments, StatefulSets, and DaemonSets replica status
+- **Persistent Volume Claims**: Binding status
+- **Events**: Recent warning and error events from the last hour
+
+**Example usage:**
+```
+Check the health of my cluster
+```
+
+Or with specific parameters:
+```
+Check the health of namespace production with verbose output
+```
+
+The prompt gathers comprehensive diagnostic data and presents it to the LLM for analysis, which will provide:
+1. Overall health status (Healthy, Warning, or Critical)
+2. Critical issues requiring immediate attention
+3. Warnings and recommendations
+4. Summary by component
+
+## Configuration File Location
+
+Place your prompts in the `config.toml` file used by the MCP server. Specify the config file path using the `--config` flag when starting the server.