SolidPing

Official

Overview Schema Source Related Servers Discussions Admin

List incidents

list_incidents

Read-onlyIdempotent

Retrieve active or resolved internal incidents for an organization, filtered by check, state, or time range, with cursor pagination for paging through results.

Instructions

List internal incidents (active or resolved) for the organization, filtered by check, state, or time range; the filters combine with AND. Returns {data, pagination} — total, size, and a cursor naming the last row (opaque, pass it back as cursor for the next page). order=asc lists oldest first and always returns a cursor, even on the last page, so you can store it and later resume with only the incidents started after it (rows younger than 5 s are held back). It lists new incidents only; changes to existing incidents are events (GET /events?type=incident&order=asc). Use diagnose_check for one check's incidents plus current health in one call, and get_status_page include=incidents for the customer-facing entries on a status page. Read-only: works with mcp:read tokens.

Input Schema

Name	Required	Description
`size`	No	Max results (1-100, default 20).
`with`	No	Comma-separated extra fields: check — include the underlying check (slug, type, config) Example: "check".
`order`	No	Sort order on start time: "desc" (default, newest first) or "asc" (oldest first; the cursor then means strictly after, and is always returned).
`since`	No	Lower bound on incident start time (RFC3339), e.g. "2026-05-03T00:00:00Z".
`state`	No	Comma-separated incident states. Allowed: active, resolved. Example: "active" or "active,resolved".
`until`	No	Upper bound on incident start time (RFC3339), e.g. "2026-05-04T00:00:00Z".
`cursor`	No	Opaque pagination cursor returned by a previous response. Omit on the first page.
`checkUid`	No	Comma-separated check UIDs or slugs to filter by, e.g. "api-prod,db-prod".

Output Schema

Name	Required	Description	Default
`data`	No	Incidents on this page.
`pagination`	No	Page state for the filter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.42.0Oct 27, 2026

addedInput schema / properties / checkUid / maxLength
```
Added value: +2048
```
addedInput schema / properties / cursor / maxLength
```
Added value: +2048
```
addedInput schema / properties / cursor / minLength
```
Added value: +1
```

addedInput schema / properties / order

Added value: +{
+  "description": "Sort order on start time: \"desc\" (default, newest first) or \"asc\" (oldest first; the cursor then means strictly after, and is always returned).",
+  "maxLength": 2048,
+  "type": "string"
+}

addedInput schema / properties / since / maxLength
```
Added value: +2048
```
addedInput schema / properties / state / maxLength
```
Added value: +2048
```
addedInput schema / properties / until / maxLength
```
Added value: +2048
```
addedInput schema / properties / with / maxLength
```
Added value: +2048
```

changedOutput schema / properties / pagination / properties / cursor / description

Previous value: -"UID of the last incident on a full page; not applied when passed back."New value: +"Opaque cursor naming the last incident; pass it back as cursor."

Changed2 schema fields changedv0.41.0Oct 23, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / additionalProperties
```
Added value: +false
```

Changed1 schema field changedv0.38.5Oct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Incidents on this page.",
+      "items": {
+        "properties": {
+          "check": {
+            "description": "Underlying check, when requested with with=check.",
+            "type": "object"
+          },
+          "checkName": {
+            "description": "Name of that check.",
+            "type": "string"
+          },
+          "checkSlug": {
+            "description": "Slug of that check.",
+            "type": "string"
+          },
+          "checkUid": {
+            "description": "UID of the check the incident is about.",
+            "type": "string"
+          },
+          "description": {
+            "description": "Custom description, when one was set.",
+            "type": "string"
+          },
+          "failureCount": {
+            "description": "Number of failures recorded for the incident.",
+            "type": "integer"
+          },
+          "kind": {
+            "description": "What the incident is about: check, slo_burn or degraded.",
+            "type": "string"
+          },
+          "number": {
+            "description": "Short per-org reference, e.g. 42.",
+            "type": "integer"
+          },
+          "relapseCount": {
+            "description": "Number of times the incident reopened.",
+            "type": "integer"
+          },
+          "resolvedAt": {
+            "description": "RFC3339 timestamp when it resolved; absent while active.",
+            "type": "string"
+          },
+          "startedAt": {
+            "description": "RFC3339 timestamp when the incident opened.",
+            "type": "string"
+          },
+          "state": {
+            "description": "active or resolved.",
+            "type": "string"
+          },
+          "title": {
+            "description": "Custom title, when one was set.",
+            "type": "string"
+          },
+          "uid": {
+            "description": "Incident UID.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pagination": {
+      "description": "Page state for the filter.",
+      "properties": {
+        "cursor": {
+          "description": "UID of the last incident on a full page; not applied when passed back.",
+          "type": "string"
+        },
+        "size": {
+          "description": "Page size used for this response.",
+          "type": "integer"
+        },
+        "total": {
+          "description": "Total incidents matching the filter.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedv0.32.1Sep 26, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real behavior: pagination cursor semantics, that order=asc always returns a cursor, that rows younger than 5s are held back, and the mcp:read token requirement. It stops short of describing rate limits or error behavior, but carries substantial beyond-annotation context.

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

Conciseness4/5

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

Front-loaded with purpose, then pagination, then alternatives. It is a dense single paragraph but every sentence contributes; slightly heavier than ideal but no filler.

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?

An output schema exists and the description nonetheless previews the return shape ({data, pagination}, cursor meaning), covers pagination and ordering semantics, and names alternatives. Nothing a caller needs to invoke correctly is missing.

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 baseline is 3; the description adds value by stating filters combine with AND, explaining cursor round-tripping, and clarifying that order=asc upgrades cursor meaning to 'strictly after.' These go beyond the schema text and help correct invocation.

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

Purpose5/5

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

States a specific verb and resource ('List internal incidents'), scopes it to active or resolved, and enumerates filter dimensions. It explicitly distinguishes itself from events ('It lists new incidents only; changes to existing incidents are events'), so an agent can tell it apart from siblings like get_incident and diagnose_check.

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

Usage Guidelines5/5

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

Explicitly routes to alternatives: 'Use diagnose_check for one check's incidents plus current health in one call, and get_status_page include=incidents for the customer-facing entries.' It also names the exclusion (events endpoint for changes), giving clear when/when-not guidance.

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