Get who is on-call next
jsm_get_next_on_callGet the responders for the next on-call shift and its start time. Use it for handover messages or to decide if an alert can wait for the next rotation.
Instructions
Return the responders who take over the next shift on a JSM schedule, and when that shift begins.
Use this for handover messages and for deciding whether an alert can wait for the next rotation.
Args:
schedule_id (string): schedule id, or name if schedule_identifier_type='name'
schedule_identifier_type ('id' | 'name'): default 'id'
date (string, optional): ISO 8601 reference point; "next" is computed relative to it. Defaults to now
flat (boolean): default true — flat list of user identifiers; false shows rotation/escalation nesting
response_format ('markdown' | 'json'): default 'markdown'
Returns (json format): { "next_on_call": { ... }, // the API response, unmodified "participants": [ // resolved, and the field to read { "id": string, "type": string, "displayName": string, "emailAddress": string } ] }
Responders are Atlassian account ids; this tool resolves them to names for you. If the credentials lack the Jira user scope the ids are still returned, with a note saying so.
Examples:
"Who picks up after this shift?" -> schedule_id=
"Who is on after the shift that covers Thursday?" -> date="2026-08-27T12:00:00Z"
"Draft a handover note" -> combine with jsm_list_alerts query="status:open"
Error handling:
HTTP 401 here while alert tools work means the token is missing read:ops-config:jira-service-management — schedules and on-call sit behind a different scope from alerts, so this is a scope gap, not a bad credential.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | ISO 8601 reference timestamp. The next shift is computed relative to this instant rather than to now, e.g. '2026-08-21T18:30:00Z'. Defaults to now. | |
| flat | No | true (default) returns a flat list of on-call user identifiers. false returns the nested structure showing which rotation or escalation each person came from. | |
| schedule_id | Yes | Schedule id, or the schedule name when schedule_identifier_type='name'. | |
| response_format | No | Output format. 'markdown' is compact and human-readable (default); 'json' returns every field for programmatic use. | markdown |
| schedule_identifier_type | No | Whether schedule_id holds an id or a schedule name. A name costs one extra lookup, because every schedule endpoint takes an id. | id |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| shift | No | ||
| next_on_call | Yes | ||
| participants | Yes |