Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Check Domain Expiry Support

checkDomainExpirySupport
Read-only

Checks whether Uptime Kuma can monitor a domain's registration expiry for a monitor ID or address. Use it before enabling domain expiry notifications, since many top-level domains lack RDAP support.

Instructions

Says whether Uptime Kuma can watch a domain's registration expiry (domainExpiryNotification), and which domain and top-level domain it would look up. Many top-level domains have no RDAP service and cannot be watched; check before switching the notification on, since Uptime Kuma accepts it either way. Pass a monitor's ID, or an address (a URL or a host name).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "checkDomainExpirySupport"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoA URL ("https://example.com/health") or host name ("db.example.com") to check instead
monitorIDNoA monitor whose address to check. Find IDs with listMonitors.

Output Schema

NameRequiredDescriptionDefault
tldNo
domainNoThe registered domain Uptime Kuma would look up
reasonNoWhy it cannot be watched
supportedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a read-only, non-open-world operation, and the description adds the genuinely useful behavioral fact that many TLDs have no RDAP service and the underlying setting will be accepted silently even when unsupported. That is exactly the kind of failure-mode context annotations cannot convey; only a note on latency or network cost is missing.

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?

Three sentences, front-loaded with the answer/output meaning, then the caveat, then the input mode. Nothing is padded, though the parenthetical domainExpiryNotification name is the only slightly heavy element.

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 shape need not be explained, and the description covers the outcome meaning, the caveat that drives usage, and both input forms. For a two-parameter read-only pre-check, an agent has everything needed to call it 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 coverage is 100%, so the schema already documents address and monitorID, including the URL-vs-host-name forms and the listMonitors pointer. The description restates the either/or input mode but never resolves the real ambiguity: both parameters are optional, so it does not say whether exactly one must be supplied or what happens if both or neither are given.

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 gives a specific verb and resource: it reports whether Uptime Kuma can watch a domain's registration expiry (naming the concrete setting, domainExpiryNotification) and which domain and TLD it would resolve. That is far more precise than the title alone and cannot be confused with the many CRUD siblings in the catalog.

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?

It explicitly frames this as a pre-flight check to run before enabling the notification, and warns that Uptime Kuma accepts the setting regardless, so the check is the only protection. It does not name a sibling or an alternative, but for a pre-validation probe there is no real alternative to route to.

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