Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

cdp_command

Executes any Chrome DevTools Protocol method on an Electron target to inspect, control, or debug app processes via Domain.method calls.

Instructions

Execute an arbitrary Chrome DevTools Protocol method on a target (Domain.method)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "method": "<method>"
    },
    "name": "cdp_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodYesCDP method name, e.g. "Page.navigate" or "Runtime.evaluate"
paramsNo
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations supply openWorldHint=true and destructiveHint=false, but the description adds no behavioral context: no statement that the return payload mirrors the raw CDP result, no error semantics for unknown methods, and no note that arbitrary protocol methods can mutate or close targets despite destructiveHint=false. For an open-world pass-through tool, that leaves the agent guessing about side effects.

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?

A single, tightly written sentence with the key concept front-loaded and no filler. It is efficient, though its brevity is under-specification rather than true economy given the tool's power.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that can invoke any CDP method, the definition omits return shape, error behavior for invalid domains/methods, and target selection logic. With no output schema and half the parameters undocumented, the description does not carry enough weight for this complexity.

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

Parameters2/5

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

Schema coverage is only 50%: 'method' and 'processId' are documented, while 'params' and 'targetId' are not. The description only echoes the already-documented '(Domain.method)' form and says nothing about how 'params' is shaped per method or how 'targetId' interacts with 'processId'.

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 names a specific verb ('Execute') and a specific resource ('an arbitrary Chrome DevTools Protocol method on a target') and clarifies the naming convention with '(Domain.method)'. It is clear what the tool does, but it draws no boundary against higher-level siblings such as evaluate or click, so an agent could not infer from this text alone when the raw escape hatch is warranted.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus the many higher-level siblings (evaluate, click, emulate, etc.) or when not to. The phrase 'arbitrary' hints at a low-level escape hatch, but the agent must infer that implication on its own.

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

Deploy Server

Other Tools