Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Test Chrome

testChrome

Starts a Chrome or Chromium binary on the Uptime Kuma host and returns its version to verify real-browser monitors can run without a remote browser.

Instructions

Starts a Chrome or Chromium binary on the Uptime Kuma host and returns its version, to check that real-browser monitors without a remote browser can run. Defaults to the chromeExecutable setting those monitors use. With no path set, Uptime Kuma looks for one, and in its Docker image INSTALLS Chromium with apt when none is there, which can take minutes. Only paths on Uptime Kuma's own list of known Chrome locations are allowed, unless its host sets UPTIME_KUMA_ALLOW_ALL_CHROME_EXEC=1. For a remote browser use testRemoteBrowser.

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

Input Schema

NameRequiredDescriptionDefault
executableNoPath of the binary to start, e.g. "/usr/bin/chromium". "" auto-detects; "#playwright_chromium" is the Chromium Playwright downloaded. Default: the chromeExecutable setting.

Output Schema

NameRequiredDescriptionDefault
okYes
versionYesThe browser version Chrome reported
executableYesWhat was tested; "" means auto-detected

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.8/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing a costly side effect: with no path set, Uptime Kuma may 'INSTALLS Chromium with apt when none is there, which can take minutes' — important because the annotations do not mark the call as read-only, and this reveals a slow, host-modifying path. It also documents the allowlist constraint and the UPTIME_KUMA_ALLOW_ALL_CHROME_EXEC=1 override that controls which paths are accepted.

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?

The purpose is front-loaded and nothing is filler, but the middle sentences are dense, run-on clauses ('With no path set, Uptime Kuma looks for one, and in its Docker image INSTALLS Chromium with apt when none is there, which can take minutes'). Splitting that into two shorter statements would read more cleanly without losing content.

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?

For a single-optional-parameter tool with an output schema, the description covers what the agent needs: what the call does, what it returns (the version), what happens on the default path, the allowlist restriction and its override, and where to go for the remote case. No material gap remains.

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 description coverage is already 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains that the default comes from the chromeExecutable setting those monitors already use, and it ties the empty-path case to auto-detection plus the possible apt install. That connection between the parameter value and runtime consequences is more than the schema provides.

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 opens with a specific verb and resource — 'Starts a Chrome or Chromium binary on the Uptime Kuma host and returns its version' — and states the goal (verifying real-browser monitors can run without a remote browser). It also explicitly distinguishes itself from the sibling testRemoteBrowser.

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 the use case ('to check that real-browser monitors without a remote browser can run') and routes the agent elsewhere for the remote case: 'For a remote browser use testRemoteBrowser.' The conditions that select this tool versus the alternative are stated outright.

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