Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Delete Incident

deleteIncident
Destructive

Permanently deletes an incident and its history from a status page. Use resolveIncident to end an incident while keeping its record, and listIncidents to find the incident ID.

Instructions

Permanently deletes an incident from a status page and its history. To end an incident but keep its record, use resolveIncident. Find the ID with listIncidents.

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": "deleteIncident"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
okYes
msgNo

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 already declare destructiveHint=true and readOnlyHint=false, so the description's job is to add specifics — and it does, by clarifying that the incident's history is destroyed along with the record and that the effect is permanent. It stops short of describing auth requirements, confirmation behavior, or failure modes for an invalid ID.

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 destructive effect, followed by the alternative and the ID lookup hint. No redundant restatement of the title or name.

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 destructive two-parameter tool with annotations covering the safety profile and an output schema covering the response, the description supplies everything needed: what is destroyed, the non-destructive alternative, and how to find the ID.

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%, with both slug and incidentID documented inline, so the baseline is 3. The description adds only the discovery pointer to listIncidents for the ID, and nothing about slug scoping beyond what the schema already says.

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 plus the scope of the effect ("permanently deletes an incident from a status page and its history"), and explicitly distinguishes itself from resolveIncident. An agent can pick between the two without opening either 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?

Gives an explicit when-not rule with the named alternative: use resolveIncident if the record should be kept. It also routes the agent to listIncidents to obtain the required ID, so both the choice and the prerequisite are covered.

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