Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

List Remote Browsers

listRemoteBrowsers
Read-only

Lists remote browsers available for real-browser monitors, so you can choose one by ID instead of built-in Chromium. Credentials are masked unless includeSecrets is true.

Instructions

Returns the remote browsers (a Chrome reachable over WebSocket, e.g. browserless) that real-browser monitors can run in instead of the built-in Chromium. A monitor uses one by ID in its remote_browser field. Tokens and logins in a URL 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": "listRemoteBrowsers"
  }
}

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
remoteBrowsersYes

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 declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds genuinely non-obvious behavior: URL credentials are masked as '***' unless includeSecrets is set, which tells the agent it will see redacted values by default. Return format details are deferred to the output schema, which is acceptable.

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 tight sentences with no filler, and the core purpose and resource definition are front-loaded. The final sentence slightly duplicates the parameter schema wording, a minor redundancy rather than bloat.

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?

With an output schema present, read-only annotations, and a single optional parameter, the description supplies what the structured fields do not: what a remote browser actually is and how monitors reference it by ID. Nothing an agent needs in order to call it correctly is missing, though cross-referencing the sibling management tools would make it stronger.

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 includeSecrets schema entry already documents the '***' behavior, the transcript-persistence consequence, the default, and the UPTIME_KUMA_INCLUDE_SECRETS override. The description's sentence about masking largely restates that, adding little beyond the schema, so the baseline of 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?

The description gives a specific verb and resource ('Returns the remote browsers') and defines the resource itself as a Chrome instance reachable over WebSocket, e.g. browserless, which real-browser monitors use instead of built-in Chromium. That is materially clearer than the name alone. It stops short of 5 because it never contrasts itself with createRemoteBrowser, testRemoteBrowser, or updateRemoteBrowser by name.

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?

Usage is only implied: the agent can infer it should call this to discover a remote browser's ID before setting a monitor's remote_browser field. There is no explicit when-to-use statement, no prerequisite guidance, and no exclusion pointing to testRemoteBrowser or createRemoteBrowser when the browser is absent.

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