Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Get Monitor Uptime

getMonitorUptime
Read-only

Retrieve a monitor's uptime percentage, check counts, ping min/avg/max, and failed periods over a chosen time range to answer questions like "What was uptime this week?"

Instructions

Returns a monitor's uptime percentage, check counts and ping (min/avg/max) over the last N hours, up to a year, with the minutes, hours or days in which checks failed, newest first. Use it for "what was the uptime this week?"; for the current status use getMonitorSummary, and for individual checks listHeartbeats. Counted as Uptime Kuma counts them: PENDING is down, and MAINTENANCE is neither.

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

Input Schema

NameRequiredDescriptionDefault
hoursNoHow far back, in hours (default: 24; e.g. 168 for a week, 720 for 30 days). Up to 24 is counted per minute, up to 720 per hour, beyond that per whole day.
monitorIDYesThe monitor to report on. Find IDs with listMonitors.

Output Schema

NameRequiredDescriptionDefault
pingYes
hoursYes
checksYes
monitorIDYes
granularityYesSize of each bucket in downtimeBuckets
uptimePercentYesup / (up + down) × 100; null when there were no checks
downtimeBucketsYesThe newest 50 of them
downtimeBucketCountYesBuckets with at least one failed check

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?

Beyond the read-only annotations, the description discloses aggregation semantics, ordering (newest first), resolution changes based on the hours parameter, and the non-obvious Uptime Kuma accounting rule that PENDING counts as down while MAINTENANCE counts as neither. These are meaningful behavioral details that reduce invocation ambiguity.

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 description is front-loaded with the core purpose and then efficiently adds usage alternatives and counting semantics. Every sentence contributes distinct information without repetition.

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 has an output schema, so return values need not be explained. With annotations covering read-only and closed-world behavior, the description provides enough scope, granularity, and accounting semantics for an agent to call the tool correctly.

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%, so the input schema already documents both parameters, including defaults, maximums, and resolution thresholds. The description reinforces the time range and example use but does not add syntax or constraints beyond what the schema provides.

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 states a specific verb and resource: returns uptime percentage, check counts, and ping min/avg/max for a monitor over a time range. It clearly distinguishes this from getMonitorSummary and listHeartbeats by naming each alternative and its purpose.

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 an explicit when-to-use example, "what was the uptime this week?", and names concrete alternatives for current status and individual checks. An agent can select the right tool without inferring missing alternatives.

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