Skip to main content
Glama
chrome-remote-debugging-mcp

chrome-remote-debugging-mcp

by danilin-em

ping

Verifies connectivity to Chrome's DevTools endpoint and reports whether the browser is reachable, returning connection details or error information.

Instructions

Check connectivity to Chrome's DevTools endpoint (CDP_URL, or the autoConnect source with CHROME_AUTOCONNECT).

Returns {"connected": True, "cdp_url", "browser", "protocol"} when Chrome answers, or {"connected": False, "cdp_url", "error": ...} when it is unreachable.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses both outcome branches, including the exact success payload (connected, cdp_url, browser, protocol) and the failure payload (connected, cdp_url, error). It does not mention whether it has side effects, whether it attempts to launch Chrome, or any timeout behavior, which keeps it below the top score.

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?

Two sentences, front-loaded with what is checked and then the return contract for both branches. No redundant restatement of the tool name and nothing extraneous.

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?

There is no output schema and no annotations, so the description must supply the return contract — and it does so precisely for both success and failure. Minor incompleteness remains around side effects and failure modes such as timeouts or whether Chrome is auto-started.

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 zero parameters, so the baseline is 4. The description usefully explains where the connection target comes from (CDP_URL env var, or the autoConnect source when CHROME_AUTOCONNECT is set), which is meaningful context an agent would otherwise lack.

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?

States a specific verb and resource: 'Check connectivity to Chrome's DevTools endpoint.' This is clearly distinguishable from siblings like navigate, evaluate, or list_tabs, which act on the browser rather than probing reachability.

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 — an agent can infer this is a prerequisite sanity check before driving Chrome, but the description never says when to prefer it over just calling browse or navigate, nor does it state any exclusions. The CDP_URL / CHROME_AUTOCONNECT note gives useful configuration context but not decision guidance.

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