Oncall

by Rootly-AI-Labs65832aa6ff7aNo licenseListed Oct 8, 2026Updated Oct 8, 2026

Show current on-call status, shift metrics, and health indicators for your team. Use to check who's on-call, handoff context, or on-call workload.

Instructions onlyDevOps & Cloud

AI-generated overview

Shows a compact on-call dashboard with current and next on-call, shift metrics, and health risk indicators.

What it does: Gathers on-call handoff context, shift workload metrics, and fatigue or health risk indicators through Rootly MCP tools, optionally scoped to a team name. It then presents a compact dashboard covering who is on-call, shift timing, incident counts, workload, and recent incidents. Sections are omitted when a data source errors or returns nothing.
When to use it: Use it to check who is currently on-call, prepare for or review a shift handoff, or assess on-call workload and fatigue risk for a team.
Requirements: Requires access to Rootly MCP tools (mcprootly*), including get_oncall_handoff_summary, get_oncall_shift_metrics, and check_oncall_health_risk. Instructions only; no scripts are shipped.

On-Call Dashboard

You are showing the user a compact on-call dashboard. Gather data and present it concisely.

Workflow

1. Gather Data

Make these calls (in parallel if possible):

mcp__rootly__get_oncall_handoff_summary -- Current and next on-call, shift context
mcp__rootly__get_oncall_shift_metrics -- Workload data (hours, incident count)
mcp__rootly__check_oncall_health_risk -- Fatigue and health risk indicators

If $ARGUMENTS contains a team name, pass it to scope the queries.

2. Present Dashboard

## On-Call Dashboard
### Current On-Call- **Who**: [name]- **Since**: [start time] ([hours] hours into shift)- **Incidents this shift**: [count]
### Next On-Call- **Who**: [name]- **Handoff**: [time] ([hours] from now)
### Shift Health- **Hours worked**: [current hours] / [shift length]- **Fatigue risk**: [LOW / MEDIUM / HIGH]- **Workload**: [incidents handled] incidents, [pages received] pages
### Recent Incidents This Shift[List of incidents handled during current shift, if any]| Severity | Title | Duration | Status ||----------|-------|----------|--------|| ... | ... | ... | ... |

## On-Call Dashboard
### Current On-Call- **Who**: [name]- **Since**: [start time] ([hours] hours into shift)- **Incidents this shift**: [count]
### Next On-Call- **Who**: [name]- **Handoff**: [time] ([hours] from now)
### Shift Health- **Hours worked**: [current hours] / [shift length]- **Fatigue risk**: [LOW / MEDIUM / HIGH]- **Workload**: [incidents handled] incidents, [pages received] pages
### Recent Incidents This Shift[List of incidents handled during current shift, if any]| Severity | Title | Duration | Status ||----------|-------|----------|--------|| ... | ... | ... | ... |

Keep the output compact. If any data source returns an error or empty result, omit that section rather than showing empty tables.

Source and attribution

Source:Rootly-AI-Labs/rootly-claude-plugininskills/oncallat commit65832aa

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Oncall

On-Call Dashboard

Workflow

1. Gather Data

2. Present Dashboard

Source and attribution

More from Rootly-AI-Labs/rootly-claude-plugin

Trend

Test

Swap

Status

Retro

Respond

More in DevOps & Cloud

M5 Onboard

Google Agents Cli Publish

Spanner Basics

Secops Cases

Managed Airflow Migrations

Managed Airflow Dag Troubleshooting