Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Delete Maintenance Window

deleteMaintenanceWindow
Destructive

Permanently removes a maintenance window by ID, returning its monitors to normal alerting when the maintenance period is no longer needed.

Instructions

Permanently deletes a maintenance window; its monitors return to normal alerting. To switch it off but keep it, use setMaintenanceWindowActive. Find the ID with listMaintenanceWindows.

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": {
      "maintenanceID": "<maintenanceID>"
    },
    "name": "deleteMaintenanceWindow"
  }
}

Input Schema

NameRequiredDescriptionDefault
maintenanceIDYesThe ID of the maintenance window to delete

Output Schema

NameRequiredDescriptionDefault
okYes
msgNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.6/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 safety is covered. The description still adds real value beyond them by disclosing the side effect that affected monitors resume normal alerting and that deletion is permanent. It doesn't mention failure behavior on a non-existent or already-deleted ID, which keeps it just short of 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?

Three short clauses, front-loaded with the destructive action and its consequence, followed by the alternative and the ID lookup. No redundant restatement of the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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, and the destructive semantics plus the ID-discovery path are covered. For a one-parameter destructive tool the definition is nearly complete, with only minor gaps such as behavior when the ID is unknown.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single maintenanceID parameter is fully documented there, so the baseline would be 3. The description earns an extra point by telling the agent where to obtain the ID (listMaintenanceWindows), which the schema does not convey.

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?

The description gives a specific verb and resource ("Permanently deletes a maintenance window") plus the resulting effect on monitors, so the agent knows exactly what the tool does. It also implicitly separates itself from the activate/deactivate sibling by emphasizing permanence.

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?

It states the when-not case explicitly ("To switch it off but keep it, use setMaintenanceWindowActive") and names the sibling that supplies the required ID ("Find the ID with listMaintenanceWindows"). Both the alternative and the prerequisite step are spelled out rather than inferred.

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