Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

List Proxies

listProxies
Read-only

Lists available proxies with protocol, host, port, and username so you can select a proxy ID for HTTP monitors; credentials stay masked unless secrets are requested.

Instructions

Returns the proxies monitors can send their requests through, with protocol, host, port and username. An HTTP-type monitor uses one by ID in its proxyId field. Passwords read "***" unless includeSecrets is set.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listProxies"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeSecretsNoReturn credentials in full instead of "***"; they then stay in the transcript. Default: false, or UPTIME_KUMA_INCLUDE_SECRETS.

Output Schema

NameRequiredDescriptionDefault
countYes
proxiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world status, yet the description still adds real behavioral detail: passwords are masked as "***" unless includeSecrets is set. This tells the agent about redaction and how to reveal credentials, which is more than the annotations provide.

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?

Three short sentences, front-loaded with what is returned, followed by the usage relationship and the secrets caveat. Efficient overall, with only mild overlap between the masking sentence and the schema's includeSecrets description.

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?

The tool is a simple read-only list with one optional parameter and an output schema, so return values need not be explained. Between the field enumeration, the proxyId usage note, and the secrets caveat, the description covers what an agent needs to call it correctly.

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?

The single parameter is documented at 100% coverage in the schema, including the default and environment-variable fallback. The description restates the masking behavior tied to includeSecrets but adds no syntax or format information beyond the schema, so baseline 3 applies.

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?

States a specific verb/resource ('Returns the proxies') and enumerates returned fields (protocol, host, port, username), so an agent knows exactly what it gets. It lacks differentiation from siblings like listAPIKeys or listDockerHosts, but the resource 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?

The sentence about an HTTP monitor using a proxy by ID in proxyId implies the tool's purpose (fetching proxy IDs for assignment), but there is no explicit when-to-use/when-not guidance or prerequisite statement. Usage is inferable rather than stated.

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