Check JSM async request status
jsm_get_request_statusCheck whether an asynchronous JSM alert action succeeded by passing the requestId returned by a write, confirming the change actually landed.
Instructions
Check whether an asynchronous alert action actually succeeded.
Every JSM alert write (acknowledge, close, add note, assign, snooze) returns immediately with a requestId and does NOT apply the change synchronously. Pass that requestId here to confirm the action landed — this is the correct way to verify a write, rather than immediately re-reading the alert and finding it unchanged.
Args:
request_id (string): the requestId returned by a write tool
response_format ('markdown' | 'json'): default 'markdown'
Returns (json format): { "action": string, // e.g. "Acknowledge" "isSuccess": boolean, "status": string, // human-readable outcome, e.g. "Alert acknowledged" "processedAt": string, // ISO 8601 "alertId": string, "alias": string }
Examples:
After jsm_acknowledge_alert returns requestId "d383c6e9-..." -> request_id="d383c6e9-..."
Error handling:
HTTP 404 shortly after a write usually means the request is still queued; wait a second and retry.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| request_id | Yes | The requestId returned by any alert write tool (acknowledge, close, note, assign, snooze). | |
| response_format | No | Output format. 'markdown' is compact and human-readable (default); 'json' returns every field for programmatic use. | markdown |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes |