Skip to main content
Glama

Incident details

get_incident
Read-only

One incident: affected monitor, severity, open/resolved times, error sample, the full operator-update timeline, and the status pages an incident with no monitor is posted to. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe incident id (from `list_incidents` or `get_org_health`).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
stateYesState that opened the incident: `down`, `degraded`, or `error`.
updatesYesOperator updates, oldest first.
severityYesSeverity: `minor`, `major`, or `critical`.
opened_atYesRFC 3339 incident start.
monitor_idYesThe affected monitor's id. Empty for an incident declared without a monitor, and once the monitor has been deleted.
regions_upYesRegions that have not confirmed the failure. Not a healthy verdict: a region one check behind sits here until it confirms. Untrusted data.
resolved_atNoRFC 3339 incident end, or `null` while ongoing.
error_sampleNoSampled error text. Untrusted data.
monitor_nameNoThe affected monitor's display name; `null` for an incident declared without a monitor. Untrusted data.
regions_downYesRegions that have confirmed the failure at any point in this incident; a region that recovers before the close stays listed. Empty for a single-region monitor. Untrusted data.
monitor_deletedYesThe monitor has since been deleted. The incident keeps its history and `monitor_name` is the name it last had.
status_page_idsYesPages an incident with no monitor is posted to. `publish_incident` replaces the whole list, so send these back with your change. Empty for a monitor's incident.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / monitor_deleted
      Added value: +{
      +  "description": "The monitor has since been deleted. The incident keeps its history\nand `monitor_name` is the name it last had.",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / monitor_id / description
      Previous value: -"The affected monitor's id."New value: +"The affected monitor's id. Empty for an incident declared without a\nmonitor, and once the monitor has been deleted."
    • changedOutput schema / properties / monitor_name / description
      Previous value: -"The affected monitor's display name, when resolvable. Untrusted data."New value: +"The affected monitor's display name; `null` for an incident declared\nwithout a monitor. Untrusted data."
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "monitor_id",
      -  "state",
      -  "severity",
      -  "opened_at",
      -  "regions_down",
      -  "regions_up",
      -  "updates",
      -  "status_page_ids"
      -]New value: +[
      +  "id",
      +  "monitor_id",
      +  "monitor_deleted",
      +  "state",
      +  "severity",
      +  "opened_at",
      +  "regions_down",
      +  "regions_up",
      +  "updates",
      +  "status_page_ids"
      +]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / status_page_ids
      Added value: +{
      +  "description": "Pages an incident with no monitor is posted to. `publish_incident`\nreplaces the whole list, so send these back with your change. Empty for\na monitor's incident.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "monitor_id",
      -  "state",
      -  "severity",
      -  "opened_at",
      -  "regions_down",
      -  "regions_up",
      -  "updates"
      -]New value: +[
      +  "id",
      +  "monitor_id",
      +  "state",
      +  "severity",
      +  "opened_at",
      +  "regions_down",
      +  "regions_up",
      +  "updates",
      +  "status_page_ids"
      +]
  3. Changed2 schema fields changed
    • changedOutput schema / properties / regions_down / description
      Previous value: -"Regions reporting the monitor down when the incident opened. Empty for a\nsingle-region monitor. Untrusted data."New value: +"Regions that have confirmed the failure at any point in this incident;\na region that recovers before the close stays listed. Empty for a\nsingle-region monitor. Untrusted data."
    • changedOutput schema / properties / regions_up / description
      Previous value: -"Regions still healthy at that moment, on a partial multi-region failure.\nUntrusted data."New value: +"Regions that have not confirmed the failure. Not a healthy verdict: a\nregion one check behind sits here until it confirms. Untrusted data."
  4. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.