Skip to main content
Glama
DavidFuchs

mcp-uptime-kuma

by DavidFuchs

List Monitors

listMonitors

Retrieve detailed configuration of all uptime monitors, filtered by type, tags, keywords, or status, to inspect or adjust settings.

Instructions

Retrieves configuration details for all monitors (URLs, check intervals, notification settings, etc.). Use this when you need to examine or modify monitor settings. For status checks ("how is everything doing?", "what's down?"), 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). Supports filtering by keywords, type, active/maintenance status, tags, and parent group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoFilter by tag name and optional value. Comma-separated for multiple tags. Format: "tagName" or "tagName=value". Monitor must have all specified tags. Case-insensitive. Examples: "production", "env=staging", "production,region=us-east"
typeNoFilter by monitor type(s). Comma-separated for multiple types. Use listMonitorTypes tool to see all available types.
activeNoFilter by active status. true=only active monitors, false=only inactive monitors.
keywordsNoSpace-separated keywords to filter monitors by pathName (case-insensitive fuzzy match). All keywords must match for a monitor to be included.
parentIdNoFilter to the DIRECT children of this group monitor. Pass null for top-level monitors (those with no parent). Not recursive — use the group's own childrenIDs to walk deeper.
maintenanceNoFilter by maintenance status. true=only monitors in maintenance, false=only monitors not in maintenance.
includeSecretsNoReturn 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.
includeTypeSpecificFieldsNoInclude 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
NameRequiredDescriptionDefault
countYes
monitorsYesArray of monitor objects 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.
Install Server

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral context. It discloses default output fields (common fields + uptime/avgPing), the effect of includeTypeSpecificFields, and a security-relevant detail about includeSecrets persisted in transcripts. It doesn't mention every internal behavior, but for a read-only list tool it's sufficiently transparent.

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 purpose, moves to differentiation, then parameter behavior, then filter capabilities. Every sentence contributes useful information without redundancy or filler. It's appropriately sized for a complex list tool.

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 description covers purpose, alternatives, default behavior, field variance, secret exposure, and full filter capabilities—all relevant for an agent to choose and invoke correctly. With no required parameters and an output schema present, this description fully completes the context needed for this tool.

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?

The input schema already has 100% coverage for parameters, but the description enriches semantics by explaining the inclusion of type-specific fields (e.g., url for HTTP, hostname/port for TCP) and emphasizing the privacy implications of includeSecrets. This adds value beyond the schema definitions.

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?

Description clearly states it retrieves configuration details for all monitors with a specific list of content (URLs, intervals, notification settings). It also distinguishes itself from getMonitorSummary, ensuring the agent learns exactly when to choose this tool over a sibling.

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?

Explicitly states when to use this tool (examine/modify settings) versus when to use getMonitorSummary for status checks. This is a clear usage directive with a named alternative, eliminating ambiguity for an agent.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DavidFuchs/mcp-uptime-kuma'

If you have feedback or need assistance with the MCP directory API, please join our Discord server