Investigate runtime changes
Explain a slow, failed or intermittent synchronisation using job history and operational baselines. Guide-derived workflow; compare with the current six-tool MCP surface.
This is an operational workflow, not an additional callable MCP tool. See the six current tools.
Operator question
What changed relative to a normal run, and what evidence supports that conclusion?
The guide describes comparing current duration with historical medians and high percentiles, then checking waits, blocking, retries and failure messages.
Context a call would need
- Job or operation identity
- Current run and baseline window
- Related server, database and schedule context
Evidence to return
- Duration variance and recent outcomes
- Step failures, retries, waits and blocking signals
- Likely operational neighbours for triage
Safety and availability
The current server does not expose job history, waits, blocking or runtime baselines. This investigation requires other data sources.