Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Clear All Statistics

clearAllStatistics
Destructive

Deletes all monitor heartbeats and uptime statistics, restarts active monitors, and keeps monitors and settings. Use only after explicit confirmation because the reset cannot be undone.

Instructions

Deletes the heartbeats and uptime statistics of EVERY monitor, and restarts the active ones; monitors and settings are kept. Cannot be undone. Only when the user explicitly asks to reset all history: confirm with them first, then pass confirm: true. For one monitor use clearMonitorHeartbeats.

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": {
      "confirm": "<confirm>"
    },
    "name": "clearAllStatistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true: confirms that the user asked to delete every monitor's history

Output Schema

NameRequiredDescriptionDefault
okYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds the details annotations cannot carry: exactly what data is removed, what survives (monitors and settings), that active monitors are restarted, and that the operation is irreversible. The required user-confirmation step is also surfaced, which is the key behavioral safeguard for a destructive bulk operation.

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 tight sentences, front-loaded with the destructive scope and followed by irreversibility, the confirmation prerequisite, and the sibling alternative. Every clause carries actionable information with 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?

For a destructive, irreversible bulk operation, the description covers scope, retained state, side effects, irreversible nature, confirmation workflow, and the single-monitor alternative. An output schema exists and annotations cover the safety profile, so no essential information is missing.

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 confirm flag is already documented with const true, so the schema does most of the work. The description still adds procedural meaning by explaining that the user must be asked first and confirm passed only afterward, which is a usage-level semantic the schema alone doesn't 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?

States a specific verb (deletes) and precise scope (heartbeats and uptime statistics of EVERY monitor), plus the side effects (restarts active monitors, keeps monitors and settings). It explicitly names the single-monitor sibling clearMonitorHeartbeats, so an agent can distinguish it 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 gating condition ('Only when the user explicitly asks to reset all history'), a required workflow (confirm with them first, then pass confirm: true), and the alternative for the narrower case ('For one monitor use clearMonitorHeartbeats'). Nothing about when or when-not to call it is left implicit.

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