mcp-uptime-kuma

Get Monitor

getMonitor

Retrieves configuration details for a specific monitor by ID, including URL, interval, and notification settings. Use to view or change monitor settings; use the summary tool for current status.

Instructions

Retrieves configuration details for a specific monitor by ID (URL, check interval, notification settings, etc.). Use this when you need to examine or modify settings for a specific monitor. For current status, use getMonitorSummary instead. By default returns only common fields plus runtime data (uptime, avgPing); set includeTypeSpecificFields to true to include type-specific fields (e.g., url for HTTP, hostname/port for TCP).

Input Schema

TableJSON Schema

Name	Required	Description
`monitorID`	Yes	The ID of the monitor to retrieve
`includeSecrets`	No	Return credentials in full instead of "***". Off by default: this output is persisted in conversation transcripts and logs. Can also be enabled globally with UPTIME_KUMA_INCLUDE_SECRETS=true.
`includeTypeSpecificFields`	No	Include type-specific fields (url, hostname, port, etc.) in addition to common fields. Default: false. When false, only returns MonitorBase fields plus uptime/avgPing.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`monitor`	Yes	Monitor object with common fields plus uptime/avgPing. May include type-specific fields when includeTypeSpecificFields is true. Credentials (pushToken, basic_auth_pass, bearer_token, headers, ...) read "***" unless includeSecrets is set.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.11.22Oct 7, 2026
- changedOutput schema / properties / monitor / properties / interval / description
```
Previous value: -"Check interval in seconds (20-2073600)"New value: +"Check interval in seconds (min 20; no upper bound since Uptime Kuma 2.5.0)"
```
- removedOutput schema / properties / monitor / properties / interval / maximum
```
Removed value: -2073600
```

Changed2 schema fields changedv0.11.9Aug 21, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv0.0.0-devAug 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and it does useful work: it discloses the default return shape (common fields plus uptime/avgPing), the opt-in for type-specific fields, and hints at the read-only nature. It does not address authentication/permission requirements or rate limits, which is the remaining gap for an unannotated tool.

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 sentences, front-loaded with purpose, then usage/alternative, then parameter behavior. No filler and every sentence adds routing or behavioral value.

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?

An output schema exists, so return-value explanation is unnecessary. For a 3-param read tool, the description covers purpose, the key alternative, and the non-obvious default/flag behavior, leaving nothing critical for correct invocation.

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%, so the baseline is 3, but the description adds meaning beyond the schema by explaining when includeTypeSpecificFields matters and giving concrete examples ('url for HTTP, hostname/port for TCP'). This contextualizes the parameter beyond its terse schema text.

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 ('Retrieves configuration details for a specific monitor by ID') and enumerates the returned content (URL, check interval, notification settings). It explicitly distinguishes itself from the sibling getMonitorSummary, so an agent can route 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative explicitly ('For current status, use getMonitorSummary instead') and gives the condition. The 'examine or modify settings' phrasing is slightly muddled since actual modification belongs to updateMonitor, but the guidance is otherwise clear with no exclusion caveats beyond the summary/settings split.

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