Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

click

Clicks the center of a CSS selector in an Electron app via CDP mouse events to simulate real user interaction during debugging.

Instructions

Click the center of a CSS selector via CDP Input.dispatchMouseEvent

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

Input Schema

NameRequiredDescriptionDefault
refNoAccessibility element ref (e.g. 'e1', 'e12') from snapshot
buttonNo
selectorNoCSS selector to click
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.9/5.0
Behavior3/5

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

The dispatchMouseEvent detail is genuinely useful: it tells the agent a real synthesized mouse event is fired at the element's center rather than a DOM-level click, which matters for scroll-into-view and hit-testing behavior. It does not say whether the element must be visible or scrolled into view, what happens on failure, or what is returned; with destructiveHint=false covering only the safety profile, this is a partial but real addition.

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 front-loaded sentence with zero filler; the verb and mechanism come first. It is telegraphic to the point of dropping useful context, but nothing in it is redundant.

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?

Five parameters, no output schema, and a single weak annotation mean the description must carry most of the burden, yet it omits when to use it, whether ref/targetId/processId are alternatives to selector, and what a caller should expect on failure or on a hidden element.

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 60%, and the description adds nothing for the undocumented parameters (button, targetId). It only restates that selector is a CSS selector, so the roughly half of the surface not described in the schema stays opaque.

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 target ("Click the center of a CSS selector") and names the underlying mechanism (CDP Input.dispatchMouseEvent). This is far more concrete than the tool name alone, though it never names click_ax as the ref-based alternative, so differentiation from siblings is left implicit.

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?

No guidance on when to prefer this over click_ax or click_menu_item, and no stated preconditions. The only usable cue is that it targets a CSS selector, which an agent must infer as the selection criterion for choosing this tool.

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