Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Get Monitor Type Fields

getMonitorTypeFields
Read-only

Get 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

NameRequiredDescriptionDefault
typeYesThe monitor type, e.g. http, mqtt, snmp. Use listMonitorTypes for all options.

Output Schema

NameRequiredDescriptionDefault
typeYes
notesYesDefaults applied when a field is omitted, and fields that become required depending on another
optionalYesOther fields this type uses
requiredYesFields a monitor of this type cannot work without. A create or type change without them is refused.
descriptionYesWhat this monitor type checks
commonFieldsYesFields every monitor type accepts, described on createMonitor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.17.0
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Addedv0.13.0

TDQS

A4.5/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 safety is covered. The description adds genuine behavioral context beyond that: it discloses that this is a self-describing metadata lookup whose value is only realized before a write, and warns that the write tools omit this information. It does not mention caching, cost, or behavior for an unknown type, so it stops short of a 5.

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 tight sentences, front-loaded with what the tool returns, then when to call it, then where type names come from. Every clause carries information an agent needs; nothing is repeated or padded.

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?

An output schema exists, so the description need not document return structure, and it correctly spends its words on purpose, sequencing, and prerequisite instead. For a one-parameter, read-only introspection tool gated to a create/update workflow, 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?

With a single parameter at 100% schema description coverage, the schema already explains that 'type' is the monitor type and points to listMonitorTypes for options. The description's 'Type names come from listMonitorTypes' restates what the schema already says, adding no syntax, format, or error-handling detail beyond it. Baseline 3 applies.

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 description names a specific verb and resource ('Describes the fields one monitor type takes') and enumerates exactly what is returned: required/optional status, meaning, accepted values, defaults, and top-level vs. typeFields placement. This is clearly distinguishable from listMonitorTypes (which enumerates type names) and from createMonitor/updateMonitor (which consume the fields).

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 states explicit when-to-use conditions: call before createMonitor, and before updateMonitor changes a type or type-specific field, with the reason ('those tools do not describe these fields'). It also routes the agent to listMonitorTypes as the source of valid type names, so no alternative is left to inference.

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