Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

health_check

Verifies Google Chrome is running with CDP enabled and accessible, helping diagnose browser connection issues before running automation.

Instructions

Check if Google Chrome is running with CDP and accessible

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It conveys that this is a non-mutating readiness check and names the CDP requirement, but says nothing about what happens on failure (error vs. false result), whether a retry is meaningful, or how the outcome is reported back.

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?

A single short sentence with the key qualifier (CDP) up front and no filler. Nothing here could be trimmed without losing information.

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 a zero-parameter health probe this is nearly complete; the only meaningful gap is that no output schema exists, so the description could have stated what a positive and negative result look like. Everything else an agent needs to call it is present.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is empty and consistent with the description's framing as a zero-input check.

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 and subject: checks whether Chrome is running with CDP enabled and accessible. This is unmistakably distinct from the action-oriented siblings (click, open_url, take_screenshot), which all presuppose a working connection, though the description never explicitly frames itself that way.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternative named. Usage is only implied: an agent can infer it is a pre-flight connectivity probe before invoking browser actions, but that inference is left to the reader.

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