Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

List Incidents

listIncidents
Read-only

Retrieve a status page's incidents newest first, including resolved ones, with cursor-based pagination to fetch the next 10.

Instructions

Returns a status page's incidents, newest first, 10 per call, resolved ones included; pass nextCursor back as cursor for the next 10. An incident shows on the page while it is both pinned and active. getStatusPage also returns the ones showing now.

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": {
      "slug": "<slug>"
    },
    "name": "listIncidents"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe status page slug. Find slugs with listStatusPages.
cursorNonextCursor from the previous call, for the next page

Output Schema

NameRequiredDescriptionDefault
totalYesIncidents on this page in all
hasMoreYes
incidentsYes
nextCursorYesPass as cursor for the next page; null on the last

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnly and non-open-world; the description adds real behavioral context: ordering is newest first, page size is fixed at 10, resolved incidents are included, and continuation is via passing nextCursor back as cursor. It also defines the 'showing' semantics (pinned AND active), which an agent cannot infer from the schema or annotations.

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?

Three short sentences, front-loaded with the core return contract, followed by the disambiguation note. Every clause carries information about ordering, page size, inclusion, or sibling choice; nothing is padding.

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?

With only two parameters, full schema coverage, an output schema, and read-only annotations, the description supplies everything an agent needs: pagination mechanics, ordering, and what the results include. No material gap remains for correct invocation.

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% and the schema already documents both slug and cursor, including where to find slugs. The description restates the cursor round-trip ('pass nextCursor back as cursor') which marginally reinforces usage but adds little beyond the schema text; baseline 3 is appropriate.

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 (returns a status page's incidents) plus scope details that make it identifiable: newest first, 10 per call, resolved included. It also distinguishes itself from getStatusPage by noting that sibling returns only the currently showing incidents.

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?

It creates a clear selection rule via 'getStatusPage also returns the ones showing now' plus the pinned-and-active definition, implying this tool is for the full/archived list while getStatusPage is for the live view. The routing is conveyed by implication rather than a directive 'use X instead when Y', so it falls short of fully explicit when-to-use guidance.

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