Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Update Proxy

updateProxy
DestructiveIdempotent

Modify an existing Uptime Kuma proxy by changing only the fields you provide, such as host, port, protocol, or credentials, and optionally set it as default or apply it to existing monitors.

Instructions

Changes a proxy. Only the fields you pass change; a password sent back as "***" keeps the stored one. Clear username (pass "") to stop sending a login. Find the ID with listProxies.

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": {
      "proxyID": "<proxyID>"
    },
    "name": "updateProxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoNew host name or IP address
portNoNew port
defaultNoMake it the proxy the web UI preselects for new monitors; the previous default stops being one
proxyIDYesThe ID of the proxy to change
passwordNoA credential: "***" keeps the stored one
protocolNoNew protocol: http, https, socks, socks5, socks5h, socks4
usernameNo"" stops sending a login
applyExistingNoAlso route every existing monitor through this proxy now. One-off: it is not stored.
includeSecretsNoReturn credentials in full instead of "***"; they then stay in the transcript. Default: false, or UPTIME_KUMA_INCLUDE_SECRETS.

Output Schema

NameRequiredDescriptionDefault
okYes
proxyNo
proxyIDYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond annotations, it discloses partial-update behavior (only passed fields change), the "***" password sentinel that preserves the stored credential, and that passing an empty username stops sending a login. These are meaningful behavioral details. It does not elaborate on the destructive or idempotent implications already covered by 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?

Four short, front-loaded sentences with no filler. The core partial-update rule appears first, followed by the two sentinel behaviors and the ID lookup pointer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an update tool with full schema coverage, destructive/idempotent annotations, and an output schema, the description covers the essential non-obvious semantics. It could mention the one-off nature of applyExisting or the default-switching side effect, but those are documented in the schema.

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 coverage is 100%, and the description reiterates the password and username sentinel semantics that are already documented in the schema. It adds no meaning for default, applyExisting, or includeSecrets beyond what the parameter descriptions provide, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Changes a proxy") and points to listProxies for ID lookup, so an agent understands the operation. It does not explicitly distinguish itself from createProxy or deleteProxy, but the mutation scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies usage on an existing proxy and tells the agent where to find the ID via listProxies. However, it gives no explicit when-not-to-use guidance or comparison to createProxy for new proxies, leaving selection inferred from the tool names.

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