Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

List Notification Types

listNotificationTypes
Read-only

Lists all notification types Uptime Kuma supports, returning the exact, case-sensitive type string createNotification requires so you can pick a valid notification type.

Instructions

Returns every notification type Uptime Kuma supports (Slack, email, ntfy, Telegram, webhooks and about a hundred more) with the exact, case-sensitive type string createNotification takes. An older Uptime Kuma may lack the newest ones. For the fields a type takes, call getNotificationTypeFields.

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": "listNotificationTypes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYes
typesYesArray of notification types

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: results are version-dependent (an older Uptime Kuma may lack the newest types) and the returned strings are case-sensitive and must be passed verbatim to createNotification. It stops short of describing ordering or size, which is a minor gap given the output schema exists.

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 what the tool returns and why it matters, followed by the version caveat and the sibling hand-off. No filler or restatement of the name.

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?

For a zero-parameter, read-only list tool with an output schema, the description covers everything an agent needs: purpose, version-dependency caveat, case-sensitivity of the returned strings, and where to go next for field-level detail.

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 tool takes zero parameters, so the baseline is 4. The description still adds useful semantics about the returned values — that type strings are case-sensitive and must match exactly when handed to createNotification.

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 — returns every notification type Uptime Kuma supports — and pairs it with the concrete downstream use: the exact, case-sensitive type string createNotification takes. It also distinguishes itself from getNotificationTypeFields by pointing there for per-type field details.

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?

Implicitly and clearly establishes when to call it (to obtain the type string for createNotification) and explicitly routes to the sibling getNotificationTypeFields for field schemas, so the agent never has to guess which of the two tools to use. Examples of type values (Slack, ntfy, Telegram, webhooks) further ground the usage context.

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