Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Create Notification

createNotification

Creates an Uptime Kuma notification channel from a name, type, and type-specific config fields, refusing incomplete required fields. Attach it to monitors via notificationIDList or applyExisting.

Instructions

Creates a notification channel from a name, a type and that type's config fields. Choose the type with listNotificationTypes, then call getNotificationTypeFields for its field names: both are case-sensitive. A create that lacks a documented required field is refused rather than saved as a channel that never sends. Attach the channel with notificationIDList on createMonitor / updateMonitor, or pass applyExisting. A repeat call creates a second channel; to change one use updateNotification.

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": {
      "name": "<name>",
      "type": "<type>",
      "config": "<config>"
    },
    "name": "createNotification"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesHuman-readable name for this notification channel
typeYesNotification type, e.g. slack, smtp, PagerDuty. Use listNotificationTypes for all options.
configYesThe fields of this notification type, e.g. {"slackwebhookURL": "https://hooks.slack.com/…"} for slack. Call getNotificationTypeFields for the names.
isDefaultNoEnable by default for new monitors
applyExistingNoAttach this channel to every existing monitor now

Output Schema

NameRequiredDescriptionDefault
idNo
okYes
msgNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses validation behavior ('a create that lacks a documented required field is refused rather than saved'), non-idempotent duplication semantics (consistent with idempotentHint=false), and the blast radius of applyExisting ('attach this channel to every existing monitor now'). These are the practical risks an agent needs before calling a create tool.

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?

It is front-loaded with the core action and every sentence carries operational content with no filler. Some sentences pack two distinct ideas (attachment options; the case-sensitivity warning), making it denser than ideal, but nothing is extraneous.

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 5-parameter create tool with a nested config object, it covers required-field validation, type discovery, duplication behavior, and downstream attachment, and an output schema exists so return values need no explanation. An agent has enough information to call it correctly on the first attempt.

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 description coverage is 100%, so name, type, config, isDefault, and applyExisting are already documented in the input schema, including the pointer to listNotificationTypes for type values. The description reinforces the lookup path for type/config fields but adds little meaning that the schema does not already carry, matching the baseline for full-coverage schemas.

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 first sentence names a specific verb and resource ('Creates a notification channel') and scopes the input to name, type, and that type's config fields. It immediately distinguishes itself from sibling updateNotification by stating that a repeat call creates a second channel rather than modifying one.

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 gives an explicit discovery sequence (listNotificationTypes, then getNotificationTypeFields, both case-sensitive) and names the exact alternatives for related goals: updateNotification to change a channel, createMonitor/updateMonitor with notificationIDList or applyExisting to attach it. When-to-use versus when-not-to-use is fully covered.

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