Phare

Update an incident

update_incident

DestructiveIdempotent

Update an incident by ID, the fields left out keep their current value. A monitors list replaces the affected monitors of a manual incident and is ignored on the incidents opened by monitors. Setting recovery_at on an ongoing incident recovers it and triggers the uptime.incident.recovered alert rules, and the changes are logged in its timeline.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "incident_id": "<incident_id>"
    },
    "name": "update_incident"
  }
}

Input Schema

Name	Required	Description
`tags`	No	Resource tags, made of lowercase letters, numbers, `.`, `_`, `:` and `-`. An organization can have up to 200 tags.
`title`	No	Incident title
`impact`	No	Incident impact
`monitors`	No	List of monitors linked to the incident
`project_id`	Yes	ID of the project to act on, see whoami
`description`	No	Description of the error that caused the incident
`incident_at`	No	Date of incident confirmation, defaults to the current date on creation. Must be within the last year and no more than 10 minutes in the future.
`incident_id`	Yes	ID of the incident to update
`recovery_at`	No	Date of incident recovery. Must be after `incident_at`, within the last year and no more than 10 minutes in the future. Cannot be removed once the incident is recovered.
`exclude_from_downtime`	No	Flag to exclude the incident from downtime calculations

Output Schema

Name	Required	Description
`id`	No
`slug`	No	Incident unique slug name
`tags`	No	Resource tags, made of lowercase letters, numbers, `.`, `_`, `:` and `-`. An organization can have up to 200 tags.
`type`	No	Incident type
`state`	No	Incident state
`title`	No	Incident title
`impact`	No	Incident impact
`status`	No	Incident status
`monitors`	No	List of monitors linked to the incident
`created_at`	No	Date of creation for the entity
`project_id`	No	Parent project ID
`updated_at`	No	Date of last update for the entity
`description`	No	Description of the error that caused the incident
`incident_at`	No	Date of incident confirmation, defaults to the current date on creation. Must be within the last year and no more than 10 minutes in the future.
`recovery_at`	No	Date of incident recovery. Must be after `incident_at`, within the last year and no more than 10 minutes in the future. Cannot be removed once the incident is recovered.
`exclude_from_downtime`	No	Flag to exclude the incident from downtime calculations

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "created_at": {
+      "description": "Date of creation for the entity",
+      "format": "date-time",
+      "type": "string"
+    },
+    "description": {
+      "description": "Description of the error that caused the incident",
+      "examples": [
+        "The server answered with an unexpected status code: 503."
+      ],
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "exclude_from_downtime": {
+      "description": "Flag to exclude the incident from downtime calculations",
+      "examples": [
+        false
+      ],
+      "type": "boolean"
+    },
+    "id": {
+      "examples": [
+        1
+      ],
+      "type": "integer"
+    },
+    "impact": {
+      "description": "Incident impact",
+      "enum": [
+        "unknown",
+        "operational",
+        "maintenance",
+        "degraded_performance",
+        "partial_outage",
+        "major_outage"
+      ],
+      "type": "string"
+    },
+    "incident_at": {
+      "description": "Date of incident confirmation, defaults to the current date on creation. Must be within the last year and no more than 10 minutes in the future.",
+      "format": "date-time",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "monitors": {
+      "description": "List of monitors linked to the incident",
+      "examples": [
+        [
+          1,
+          2,
+          3
+        ]
+      ],
+      "items": {
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    "project_id": {
+      "description": "Parent project ID",
+      "examples": [
+        1
+      ],
+      "type": "integer"
+    },
+    "recovery_at": {
+      "description": "Date of incident recovery. Must be after `incident_at`, within the last year and no more than 10 minutes in the future. Cannot be removed once the incident is recovered.",
+      "format": "date-time",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "slug": {
+      "description": "Incident unique slug name",
+      "examples": [
+        "APP-123"
+      ],
+      "type": "string"
+    },
+    "state": {
+      "description": "Incident state",
+      "enum": [
+        "unknown",
+        "investigating",
+        "identified",
+        "monitoring",
+        "resolved"
+      ],
+      "type": "string"
+    },
+    "status": {
+      "description": "Incident status",
+      "enum": [
+        "ongoing",
+        "recovering",
+        "recovered"
+      ],
+      "type": "string"
+    },
+    "tags": {
+      "description": "Resource tags, made of lowercase letters, numbers, `.`, `_`, `:` and `-`. An organization can have up to 200 tags.",
+      "items": {
+        "examples": [
+          "environment:production"
+        ],
+        "type": "string"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Incident title",
+      "examples": [
+        "Service is not working as expected"
+      ],
+      "type": "string"
+    },
+    "type": {
+      "description": "Incident type",
+      "enum": [
+        "monitor",
+        "manual"
+      ],
+      "type": "string"
+    },
+    "updated_at": {
+      "description": "Date of last update for the entity",
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedNov 7, 2026

TDQS

A4.1/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds substantial behavior beyond the annotations: partial-update semantics, replacement behavior for `monitors`, conditional ignoring on monitor-opened incidents, recovery side effects including alert rules, and timeline logging. These details help an agent understand the consequences of calling a destructive mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and dense without being wasteful. Every sentence provides relevant update behavior, conditional rules, or side effects.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich schema, annotations, and output schema, the description covers the important behavioral quirks. A minor gap is the lack of explicit routing guidance between this tool and the `recover_incident` sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for key parameters. It explains that `monitors` replaces the affected monitors on manual incidents and that `recovery_at` recovers an ongoing incident and triggers alert rules.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: update an incident by ID. It clearly implies partial update semantics, but it does not explicitly distinguish this tool from siblings such as recover_incident or create_incident.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through behavioral notes like omitted fields keeping their current value and `monitors` being ignored on monitor-opened incidents. However, it does not explicitly say when to use this instead of `recover_incident` or other incident tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Phare tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?