SolidPing

Official

Overview Schema Source Related Servers Discussions Admin

List incidents

list_incidents

Read-onlyIdempotent

Retrieve internal incidents filtered by check, state, or time range to monitor active or resolved issues. Use for tracking downtime and troubleshooting.

Instructions

List internal incidents (active or resolved) for the organization, filtered by check, state, or time range. Returns {data, pagination} — total, size, and a cursor naming the last row of a full page; the cursor is not read back on the next call yet, so move forward by narrowing since/until. 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

TableJSON 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".
`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

TableJSON 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.

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

Behavior5/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 non-obvious behavior: the cursor returned in the response is not read back on the next call yet, so advancing requires narrowing since/until, plus it discloses that mcp:read tokens suffice. Both are genuinely beyond what the structured fields convey.

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?

Four sentences, purpose-front-loaded, and each block earns its place (filters, pagination caveat, alternatives, auth). The 'Returns {data, pagination}' clause mildly duplicates the existing output schema, which keeps it from a 5.

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 read-only, 7-param, zero-required list tool with an output schema, the description covers purpose, filters, pagination behavior, sibling routing, and auth scope. Nothing an agent needs to invoke 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 size, with, since, until, state, cursor, and checkUid in detail. The description only summarizes the filter axes (check, state, time range), which maps onto the schema without adding format or edge-case detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (List) and resource (internal incidents), plus scope: organization-wide, active or resolved, filterable by check/state/time. An agent can distinguish it from get_incident (single) and from the status-page tools without opening a schema.

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 with conditions: diagnose_check when you want one check's incidents plus current health in a single call, and get_status_page include=incidents for the customer-facing entries. This is when-to-use guidance naming the sibling that wins in each case.

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