Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Clear Monitor Events

clearMonitorEvents
Destructive

Empties a monitor's event and status-change list while keeping its heartbeats and uptime statistics intact. Use it to reset event history; the action cannot be undone.

Instructions

Empties a monitor's event list, the status changes listHeartbeats returns with important: true: every heartbeat's message is blanked and none counts as a status change any more. The heartbeats and the uptime statistics are kept. Cannot be undone.

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": {
      "monitorID": "<monitorID>"
    },
    "name": "clearMonitorEvents"
  }
}

Input Schema

NameRequiredDescriptionDefault
monitorIDYesThe monitor whose events to clear. Find IDs with listMonitors.

Output Schema

NameRequiredDescriptionDefault
okYes
monitorIDYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare destructiveHint=true, but the description goes further by disclosing exactly which data is removed (heartbeat messages blanked, status-change flag cleared), which data survives (heartbeats, uptime stats), and that the operation is irreversible. That is meaningful context beyond the annotation set.

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?

Very short and front-loaded with the action, with no filler. The embedded clause describing events is a bit dense and takes a second read, but every part carries information.

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 single-parameter destructive tool with rich annotations and an output schema, the description covers the essentials: what is destroyed, what is preserved, and irreversibility. Nothing an agent needs before calling 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% and the single monitorID parameter is fully documented in the schema, including how to find IDs. The description adds no additional parameter semantics, so the baseline of 3 applies.

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 ("Empties a monitor's event list") and then defines precisely what an "event" is: the status changes listHeartbeats returns with important: true. It also distinguishes itself from related cleanup tools by naming what is kept (heartbeats, uptime statistics).

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?

The scope statement — events cleared, heartbeats and uptime statistics retained — implicitly tells the agent when to pick this tool over clearMonitorHeartbeats or clearAllStatistics. It stops short of an explicit "use X instead when..." routing sentence, so the agent must infer the alternative.

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