Get who is on-call now
jsm_get_on_callFind who is on-call for a Jira Service Management schedule now or at any past/future time, to know who to wake up and who was on-call during an incident. Returns responder names and emails.
Instructions
Return the responders currently on-call for a JSM schedule, optionally evaluated at a past or future timestamp.
This is the tool for "who do I wake up?" and, with the 'date' argument, for "who was on-call when this incident started?" — which is often the more useful question during a post-incident review.
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 timestamp to evaluate at; 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): { "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, so there is no need to look an id up elsewhere. If the credentials lack the Jira user scope the ids are still returned, with a note saying so.
Examples:
"Who's on-call for platform right now?" -> schedule_id="platform", schedule_identifier_type="name"
"Who was on-call at 03:14 UTC yesterday?" -> date="2026-08-20T03:14:00Z"
Error handling:
An empty result means nobody is rostered at that moment — a real and important answer, not a failure.
HTTP 404 means the schedule id/name is wrong; list them with jsm_list_schedules.
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 timestamp to evaluate the rotation at, e.g. '2026-08-21T18:30:00Z'. Defaults to now. Use this to answer 'who was on-call when this fired?' | |
| 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 | ||
| on_call | Yes | ||
| participants | Yes |