Skip to main content
Glama
DavidFuchs

mcp-uptime-kuma

by DavidFuchs

List Monitors

listMonitors

Retrieve details for all Uptime Kuma monitors, including URLs, check intervals, and notification settings. Filter by status, type, tags, or keywords to view or update configurations.

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, and tags.

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.
Behavior5/5

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

Even without annotations, the description discloses key behavioral traits: default fields returned (common + uptime/avgPing), how includeTypeSpecificFields expands results, and the privacy implication of includeSecrets (persisted in logs). This goes beyond schema details and is critical for safe invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and well-structured, though the filtering sentence is dense. Each sentence adds useful information without waste; slightly long but appropriate for the tool's flexibility.

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?

Given the presence of an output schema and high schema coverage, the description effectively covers purpose, alternatives, filtering, default behavior, and security concerns, making it fully complete for understanding when and how to use the 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?

Schema covers 100% of parameters with descriptions, but the tool description adds valuable semantic context about default behavior for includeTypeSpecificFields and the security sensitivity of includeSecrets, enriching parameter understanding beyond the schema.

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 clearly states 'Retrieves configuration details for all monitors' with specific examples of fields, and explicitly contrasts with getMonitorSummary for status checks, making the tool's purpose unambiguous and well-differentiated from siblings.

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 provides explicit when-to-use guidance ('examine or modify monitor settings'), names the alternative for status checks (getMonitorSummary), and describes filtering options to narrow results, giving the agent clear decision criteria.

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

Install Server

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