Skip to main content
Glama
Sign In

Phare

by io.phare.mcp
OverviewDiscussionsAdmin

List incidents

list_incidents
Read-onlyIdempotent

Get a paginated list of the incidents of the project, newest first: the ones opened by failing monitors and the manual ones. Filter them by monitor or tag.

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>"
    },
    "name": "list_incidents"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoFilter incidents by tag. Can be specified multiple times to only return incidents having all the given tags.
pageNoPage number to show
per_pageNoNumber of resources to return per page
monitor_idNoFilter incidents by monitor ID. Can be specified multiple times to filter by multiple monitor IDs.
project_idYesID of the project to act on, see whoami

Output Schema

NameRequiredDescriptionDefault
dataNo
metaNoMeta data for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "items": {
+        "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"
+      },
+      "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"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description still adds real behavioral context beyond that: deterministic ordering (newest first), pagination, and the fact that both monitor-generated and manual incidents are included.

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 front-loaded sentence with no filler; the core noun phrase and ordering come first, and the filter clause is tucked in last. Every clause carries information an agent needs.

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

Completeness5/5

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

For a simple read-only list tool with an output schema and fully documented parameters, the description covers scope, ordering, pagination, and filtering. Nothing needed to call it correctly is missing.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents page, per_page, monitor_id, tag, and project_id in detail. The description only echoes that incidents can be filtered 'by monitor or tag' without adding syntax, defaults, or multi-value behavior beyond what the schema states, so baseline 3 applies.

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 ('Get a paginated list of the incidents of the project') plus scope (newest first, both monitor-opened and manual incidents). An agent can distinguish it from get_incident (single incident) and list_incident_updates (updates) by the resource named, but no sibling is called out explicitly.

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?

The description implies when to use it by describing what it returns (all incidents of a project, filterable by monitor or tag), but it never states when to prefer it over alternatives such as get_incident for a single item or the update-timeline tools, and gives no when-not guidance.

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

All Phare toolsInspect
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