analyze_root_cause
Analyze a service symptom to identify its likely root cause by correlating recent deployments, error logs, and performance metrics, returning a confidence-scored hypothesis with supporting evidence.
Instructions
Performs automated root cause correlation for a service exhibiting a given symptom. Internally cross-references recent deployments, error logs, and service metrics to produce a structured hypothesis: {likely_cause, confidence (0–1), evidence[]}. This is the primary reasoning tool — call it after collecting data with get_recent_deployments, get_service_logs, and get_service_metrics. Confidence above 0.7 suggests high certainty.
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>",
"symptom": "<symptom>"
},
"name": "analyze_root_cause"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| service | Yes | The service that is exhibiting the symptom (e.g., "payment-service"). | |
| symptom | Yes | A concise description of the observed symptom (e.g., "high error rate", "latency spike above 500ms", "pod CrashLoopBackOff"). |