Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Resolve Incident

resolveIncident
Idempotent

Marks an incident as resolved so it disappears from a status page while remaining in incident history; permanently remove it separately if needed.

Instructions

Marks an incident as over: it leaves the status page but stays in listIncidents. To remove it from the history too, use deleteIncident. Find the ID with listIncidents or getStatusPage.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe status page slug. Find slugs with listStatusPages.
incidentIDYesThe ID of the incident to resolve

Output Schema

NameRequiredDescriptionDefault
okYes
incidentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover the safety profile (non-read-only, non-destructive, idempotent), and the description adds the key behavioral consequence: the incident disappears from the status page but persists in listIncidents. It doesn't mention auth requirements or side effects on subscribers/notifications, keeping it below a 5.

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?

Two tight sentences, front-loaded with the core effect, followed by the disambiguation and ID-lookup hint. 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 so return values need not be explained; annotations carry safety; the description supplies the one non-obvious semantic (resolved incidents remain in history) and the alternative path. Complete for this complexity.

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 both slug and incidentID are already documented, including how to find slugs. The description only adds sourcing for the incident ID (listIncidents or getStatusPage), which is useful but marginal.

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 ('Marks an incident as over') and explains the resulting scope change (leaves status page, stays in listIncidents). Clearly distinguishable from deleteIncident, which it names explicitly.

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?

Gives explicit when-to-use (resolve when the incident is over) versus an alternative (deleteIncident to remove from history) and points to listIncidents/getStatusPage for ID lookup.

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