Phare

List incident updates

list_incident_updates

Read-onlyIdempotent

Get a paginated list of the updates of an incident, the messages published on the status pages, newest first.

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": "list_incident_updates"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number to show
`per_page`	No	Number of resources to return per page
`project_id`	Yes	ID of the project to act on, see whoami
`incident_id`	Yes	ID of the incident

Output Schema

Name	Required	Description	Default
`data`	No
`meta`	No	Meta data for pagination

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "items": {
+        "properties": {
+          "content": {
+            "description": "Content of the incident update",
+            "examples": [
+              "We are investigating the issue."
+            ],
+            "type": "string"
+          },
+          "created_at": {
+            "description": "Date of creation for the entity",
+            "format": "date-time",
+            "type": "string"
+          },
+          "creator": {
+            "description": "Creator of the incident update",
+            "properties": {
+              "id": {
+                "description": "Creator ID",
+                "examples": [
+                  1
+                ],
+                "type": "integer"
+              },
+              "label": {
+                "description": "Creator label",
+                "examples": [
+                  "nicolas@phare.io"
+                ],
+                "type": "string"
+              },
+              "type": {
+                "description": "Creator type",
+                "enum": [
+                  "user",
+                  "api_key"
+                ],
+                "examples": [
+                  "user"
+                ],
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "id": {
+            "description": "Incident update ID",
+            "examples": [
+              1
+            ],
+            "type": "integer"
+          },
+          "published_at": {
+            "description": "Date of publication of the incident update, 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"
+          },
+          "state": {
+            "description": "State of the incident update",
+            "enum": [
+              "unknown",
+              "investigating",
+              "identified",
+              "monitoring",
+              "resolved"
+            ],
+            "type": "string"
+          },
+          "updated_at": {
+            "description": "Date of last update for the entity",
+            "format": "date-time",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "meta": {
+      "description": "Meta data for pagination",
+      "properties": {
+        "current_page": {
+          "examples": [
+            2
+          ],
+          "type": "integer"
+        },
+        "from": {
+          "examples": [
+            11
+          ],
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "has_more_pages": {
+          "description": "Whether a next page exists, fetched with the page argument",
+          "type": "boolean"
+        },
+        "per_page": {
+          "examples": [
+            100
+          ],
+          "type": "integer"
+        },
+        "to": {
+          "examples": [
+            20
+          ],
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedNov 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds one genuinely new behavioral fact, the newest-first ordering, but says nothing about rate limits, auth scope, or what happens with out-of-range pages, which the schema leaves silent on.

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?

A single sentence with no filler, front-loading the core action and result scope, then appending the two facts an agent most needs (status-page message semantics, newest-first order). Nothing could be removed without losing information.

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?

With an output schema present, the description need not explain return values, and the rich annotations cover the safety profile. What remains useful is that it names the sort order and the domain meaning of an update, making the definition complete enough to call correctly for a simple paginated list.

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 description coverage is 100%, so page, per_page, project_id, and incident_id are already fully documented in the schema, and the baseline would be 3. The description's phrase 'paginated list' reinforces how page/per_page are meant to be used together, giving a small semantic lift beyond the individual field descriptions.

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?

States a specific verb and resource (list updates of an incident) and adds a clarifying gloss that these are 'the messages published on the status pages,' which disambiguates from generic incident fields. It stops short of naming the sibling single-item tool get_incident_update or contrasting with list_incidents, so sibling differentiation is only implied by the 'of an incident' scoping.

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 by the phrasing: reach for this when you need the update timeline for a known incident_id. There is no explicit when-to-use vs when-not guidance, no mention of alternatives such as get_incident_update for a single update, and no stated prerequisite beyond the required IDs.

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?