List every monitored service with its team, tier and SLO targets.

Call this first when you don't already know a service name — the other tools reject names that aren't in this list.

Search a service's logs within a time window.

Use level="ERROR" to skip the noise, and contains to grep for a substring (a trace id, "timeout", an error code). Returns newest first.

Summarise one metric for one service over a window.

Returns min/mean/p95/latest plus whether the service's SLO is breached, so you get the judgement and not just the numbers.

Deploy history, newest first. Omit service for the whole fleet.

Find whether a recent deploy explains a service's current errors.

Compares error rate and p99 latency before vs. after the most recent deploy in the window, pulls matching ERROR log samples, and returns a verdict with a confidence level.

This is the tool to reach for on "why is X broken" — it does in one call what would otherwise be a get_deploys + two get_metrics + query_logs chain, and it does the before/after arithmetic for you.

File an incident. This pages the on-call engineer — use it deliberately.

Requires the incidents:write scope; read-only callers are rejected. Prefer confirming with a human before calling this: it is the one tool here with a real-world side effect.