Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Test Remote Browser

testRemoteBrowser
Read-only

Checks whether Uptime Kuma can drive a browser at a WebSocket URL without saving changes; test a new ws:// or wss:// endpoint before creation or verify a saved remote browser by ID.

Instructions

Checks that Uptime Kuma can drive a browser at a WebSocket URL, without saving anything: pass url to try one before createRemoteBrowser, or remoteBrowserID to check a saved one.

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": "testRemoteBrowser"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA ws:// or wss:// endpoint to try
remoteBrowserIDNoA saved remote browser to check

Output Schema

NameRequiredDescriptionDefault
okYes
msgNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.6/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 the safety profile is covered; the description adds the meaningful behavioral fact that nothing is persisted, which is what makes this usable as a pre-check. It does not mention what a failed check looks like (timeout, refused connection, auth rejection), so a small gap remains.

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?

One sentence, front-loaded with the action and the no-persistence guarantee, followed immediately by the two usage branches. Every clause carries information; there is no filler.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. The only shortfall is that both parameters are optional and their interaction (mutual exclusivity, precedence, behavior when neither is given) is left unstated, which matters for a two-mode test tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by mapping each parameter to a distinct intent (unsaved trial vs. existing saved browser) rather than just restating the field labels. It stops short of saying whether the two are mutually exclusive or what happens if both are supplied.

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 states a specific action (checks that Uptime Kuma can drive a browser), the resource (a WebSocket endpoint / saved remote browser), and the key scope qualifier (without saving anything). It explicitly contrasts with the sibling createRemoteBrowser, so an agent can distinguish a dry-run test from a persistent creation.

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 gives a branch-by-branch when-to-use rule: pass url to try an endpoint before createRemoteBrowser, or pass remoteBrowserID to verify an already-saved browser. The named alternative and the selection condition are both explicit, leaving nothing to inference.

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