Pingstack

List incidents

list_incidents

Read-onlyIdempotent

List incidents across the account's checks that are still open or were resolved in the last 7 or 30 days (30 by default), newest first, 20 per page. Each item has the incident id, check id and name, cause (what failed, such as an HTTP status or a missed heartbeat; null when none was recorded), started_at, resolved_at (null while open), resolved and duration_seconds, which counts up to now for open incidents. Filter by one check or by open or resolved state. Notes, status updates and notification details aren't included. next_cursor is null on the last page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_incidents"
  }
}

Input Schema

Name	Required	Description
`days`	No	Include incidents still open or resolved within this many days. Defaults to 30.
`limit`	No	Items per page, 1 to 100. Defaults to 20.
`state`	No	Only open or only resolved incidents. Omit for both.
`cursor`	No	next_cursor from the previous page. Omit for the first page; next_cursor is null on the last.
`check_id`	No	Only incidents of this check (check_…).

Output Schema

Name	Required	Description	Default
`items`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 10, 2026

addedOutput schema / properties / items / items / properties / cause
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / items / items / properties / check_name
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / items / items / required

Previous value: -[
-  "id",
-  "check_id",
-  "started_at",
-  "resolved_at",
-  "resolved",
-  "duration_seconds"
-]New value: +[
+  "id",
+  "check_id",
+  "check_name",
+  "cause",
+  "started_at",
+  "resolved_at",
+  "resolved",
+  "duration_seconds"
+]

AddedNov 9, 2026

TDQS

A4.2/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 behavior, so the description's job is to add operational detail, which it does: default window, ordering, page size, cursor termination, and the fact that duration_seconds counts up to now for open incidents. Null semantics for cause and resolved_at are also disclosed, though pagination limits beyond '20 per page' are not spelled out.

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-loads the core listing scope, then item shape, then filters, then exclusions — a sensible order with no filler sentences. It is somewhat dense and spends two sentences enumerating return fields even though an output schema exists, which is the main redundancy.

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, paginated list tool with a full schema and an output schema, the definition covers everything an agent needs: default window, ordering, page size, filter options, null-field meaning, and cursor termination. Nothing required for correct invocation 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 description coverage is 100%, so all five parameters are already documented, including defaults and enums. The description mostly restates those defaults (30 days, 20 per page) and adds only modest value such as ordering and the null-cursor termination rule; it does not clarify whether check_id and state can be combined or what happens with cursor plus filters.

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 with scope: 'List incidents across the account's checks that are still open or were resolved in the last 7 or 30 days.' It also draws a boundary by declaring that notes, status updates, and notification details are excluded, which separates it from incident-detail and incident-update siblings without needing to name them.

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

Usage Guidelines4/5

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

Gives clear usage context: default 30-day window, filtering 'by one check or by open or resolved state,' and newest-first paging. It does not explicitly say when to prefer get_incident for a single record or when to skip this tool entirely, so an agent must infer that from the exclusion sentence.

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

All Pingstack tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?