diagnose_service
Run a structured diagnostic runbook for Kubernetes workloads or services to identify root causes of slowness or failures, returning ranked hypotheses with evidence and next-step recommendations.
Instructions
RUNBOOK: status -> events -> resources/throttling -> OOM/crash -> endpoints -> JVM/pool/downstreams -> log errors -> golden signals -> recent changes. Returns ranked hypotheses with evidence and the next tool to run. Start here for 'why is X broken/slow?'.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"service": "<service>"
},
"name": "diagnose_service"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| window | No | Time window like 15m, 2h, 1d (default 30m) | |
| service | Yes | Workload name as you would say it: a Deployment, StatefulSet, DaemonSet, Service, or Pod name | |
| namespace | No | Kubernetes namespace (required: no default configured; see list_namespaces) |