Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

click_ax

Clicks an element by accessibility name (optional role) using the accessibility tree instead of CSS, enabling interaction with Electron app controls.

Instructions

Click an element by accessibility name (optional role). Uses the AX tree, not CSS.

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": {
      "name": "<name>"
    },
    "name": "click_ax"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAccessible name, e.g. "Go" or "Submit"
roleNoAX role, e.g. "button" or "link"
exactNoRequire an exact name match
buttonNo
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

A3.5/5.0
Behavior3/5

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

Annotations only supply destructiveHint=false, so the description carries the rest of the burden; it does disclose the resolution mechanism (AX tree), which is genuinely informative. It says nothing about ambiguity handling (multiple matching elements), waiting/auto-scroll behavior, or what happens when no match is found.

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 short sentences, front-loaded with the action and selector, followed by the mechanism note. No filler or redundancy.

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

Completeness3/5

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

For a 6-parameter interaction tool with no output schema and thin annotations, the description covers the core selection model but omits match-ambiguity behavior, failure modes, and the role of `targetId`/`processId`. It is adequate to attempt a call, not complete enough to predict its outcome.

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

Parameters3/5

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

Schema description coverage is 67%, and the description only restates the two parameters the schema already documents (name, optional role). It adds no meaning for `exact`, `button`, `targetId`, or `processId`, two of which lack schema descriptions entirely.

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 (Click), the selector mechanism (accessibility name, optional role), and the underlying technique (AX tree, not CSS). This implicitly distinguishes it from the plain `click` sibling, but it never names that sibling, so the differentiation is inferred rather than stated.

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?

The phrase 'Uses the AX tree, not CSS' hints at when this is the right choice over a CSS-based click, which is useful implied guidance. However, there is no explicit when-to-use/when-not-to-use statement and no reference to alternatives such as `click` or `type_ax`.

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