Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Get Notification Type Fields

getNotificationTypeFields
Read-only

Returns required and optional configuration fields, with meanings, for a notification type so you can create or update Uptime Kuma notification settings correctly.

Instructions

Describes the config fields one notification type takes: which are required, which are optional and what each means. Call it before createNotification, or before updateNotification changes a type or its settings: field names are case-sensitive and Uptime Kuma saves a misspelled one without complaint. The common types are covered; for the rest it says so, and their field names can be copied from an existing channel in listNotifications. Type names come from listNotificationTypes.

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

Input Schema

NameRequiredDescriptionDefault
typeYesThe notification type, e.g. slack, smtp, PagerDuty. Use listNotificationTypes for all options.

Output Schema

NameRequiredDescriptionDefault
nameYesThe name Uptime Kuma shows for this type
typeYes
notesYes
optionalYesOther fields the type reads
requiredYesFields the type cannot send without. A create without them is refused.
documentedYesfalse when this server has no field table for the type
commonFieldsYesArguments of createNotification / updateNotification that every type takes, outside config

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, and nothing contradicts them. Beyond that, the description adds genuinely useful behavior: field names are case-sensitive and Uptime Kuma silently saves misspelled ones, and uncommon types are only partially covered. That is exactly the kind of hazard an agent could not infer from schema or annotations.

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, then when to call it, then the caveat about unsupported types. Every sentence carries distinct information with no filler.

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 one-parameter read-only lookup with an output schema, the description covers purpose, timing relative to create/update, the case-sensitivity hazard, and the fallback path for uncovered types. Nothing an agent needs in order 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single 'type' parameter is already documented with examples and a pointer to listNotificationTypes. The description repeats the listNotificationTypes guidance but adds semantics about the type argument only indirectly, through its coverage caveat. Baseline 3 is appropriate.

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: it describes the config fields a notification type takes, including which are required, optional, and what each means. This is clearly distinguishable from siblings like createNotification or getMonitorTypeFields, which operate on different resources.

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?

Explicitly says to call it before createNotification and before updateNotification changes a type or its settings. It also covers the fallback when a type isn't supported (copy field names from an existing channel in listNotifications) and where type names come from (listNotificationTypes), leaving little to inference.

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