Get Monitor Type Fields
getMonitorTypeFieldsGet required and optional fields, defaults, and placement for a specific Uptime Kuma monitor type before creating or updating monitors.
Instructions
Describes the fields one monitor type takes: which are required, which are optional, what each means and accepts, its default, and whether it is passed at the top level or inside typeFields. Call it before createMonitor, and before updateMonitor changes a type or a type-specific field: those tools do not describe these fields. Type names come from listMonitorTypes.
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": "getMonitorTypeFields"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | The monitor type, e.g. http, mqtt, snmp. Use listMonitorTypes for all options. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | ||
| notes | Yes | Defaults applied when a field is omitted, and fields that become required depending on another | |
| optional | Yes | Other fields this type uses | |
| required | Yes | Fields a monitor of this type cannot work without. A create or type change without them is refused. | |
| description | Yes | What this monitor type checks | |
| commonFields | Yes | Fields every monitor type accepts, described on createMonitor |