Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Clear Monitor Heartbeats

clearMonitorHeartbeats
Destructive

Deletes all heartbeats and uptime statistics for one monitor, resetting its history from the next check; active monitors restart, settings stay, and the action cannot be undone.

Instructions

Deletes all of one monitor's heartbeats and uptime statistics, so its history and uptime start again from the next check; an active monitor is restarted. The monitor and its settings are kept. Cannot be undone. To clear only its event list, use clearMonitorEvents; for every monitor at once, clearAllStatistics.

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

Input Schema

NameRequiredDescriptionDefault
monitorIDYesThe monitor whose history to delete. Find IDs with listMonitors.

Output Schema

NameRequiredDescriptionDefault
okYes
monitorIDYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds the operational details an agent actually needs: the monitor and its settings survive, history restarts from the next check, an active monitor is restarted as a side effect, and the action cannot be undone. That is meaningful context beyond the safety flags, including a non-obvious restart side effect.

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?

The definition is dense but front-loaded: the destructive effect and scope come first, preservation and restart behavior follow, and alternative routing closes it out. No sentence is filler, and the semicolon structure keeps related behavior grouped.

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?

The tool is a destructive single-parameter operation and the description covers scope, preserved state, restart side effect, irreversibility, and sibling routing. An output schema exists, so return-value detail is not required, leaving no material gap for an agent deciding whether to invoke it.

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 single monitorID parameter already includes a pointer to listMonitors, so the schema does the work here. The description adds no further parameter-level detail (for example, no mention of what happens if the ID is unknown), which is appropriate at baseline 3.

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 opens with a specific verb and resource: 'Deletes all of one monitor's heartbeats and uptime statistics,' scoping it to a single monitor. It immediately distinguishes itself from clearMonitorEvents (events only) and clearAllStatistics (all monitors), so an agent can route correctly without opening any 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?

It gives explicit selection criteria: use this tool to reset one monitor's history and uptime, use clearMonitorEvents to clear only the event list, and use clearAllStatistics to affect every monitor. Both the when and the when-not are stated with named alternatives.

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