Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Test Notification

testNotification

Sends a test message through a saved Uptime Kuma notification channel to confirm its settings work and messages are delivered; use listNotifications to find the channel ID.

Instructions

Sends a test message (" Testing") through a saved notification channel, as the Test button in Uptime Kuma does, to check its settings work. It really is delivered, to Slack, email or wherever the channel points, so do not repeat it without reason. Nothing is saved. Find the ID with listNotifications.

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": {
      "notificationID": "<notificationID>"
    },
    "name": "testNotification"
  }
}

Input Schema

NameRequiredDescriptionDefault
notificationIDYesThe ID of the channel to test

Output Schema

NameRequiredDescriptionDefault
okYes
msgNoThe provider's answer, e.g. "Sent Successfully."

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?

Goes well beyond the annotations by disclosing that the message is actually delivered to an external destination (Slack, email, wherever the channel points), that nothing is persisted, and that it should not be repeated unnecessarily. This complements openWorldHint=true and idempotentHint=false with concrete consequences.

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 short sentences, front-loaded with the action, followed by the delivery warning and the ID lookup hint. Every sentence carries distinct, useful information with no padding.

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?

Covers action, side effects, safety caution, and parameter sourcing for a single-parameter tool, and an output schema exists so return values need not be described. Nothing an agent needs to call it correctly is missing.

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 schema already defines notificationID. The description adds practical meaning by telling the agent where to source that ID (listNotifications), which the schema alone does not.

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: sends a test message through a saved notification channel, mirroring the Uptime Kuma Test button. This clearly separates it from siblings like listNotifications, createNotification, and updateNotification.

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?

Explains the purpose context (verify channel settings work) and gives explicit when-to-use guidance plus a caution against repeating the call without reason. It also routes the agent to listNotifications to obtain the ID. No explicit statement of when not to use it or of an alternative verification path, but the guidance is actionable.

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