Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

snapshot

Read-only

Captures the accessibility tree with roles and names via CDP Accessibility.getFullAXTree, giving agents a clear UI map for Electron debugging.

Instructions

Accessibility tree snapshot (roles/names) via CDP Accessibility.getFullAXTree — agent-friendly UI map

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

Input Schema

NameRequiredDescriptionDefault
depthNo
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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and the description is consistent with a non-mutating read. It adds useful context by disclosing the CDP method used and what the payload contains (roles/names), but says nothing about size, truncation, performance cost, or that the tree can be large on complex pages — relevant for a tree dump.

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 dense line with the resource front-loaded and the mechanism as a parenthetical. Nothing is wasted, though the telegraphic fragment style leaves no room for the missing parameter or usage detail.

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-required-parameter read tool with no output schema, stating the source method and payload shape (roles/names) covers the essentials of what an agent gets back. The depth parameter's effect on the result is the notable omission.

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 33% — only processId is documented. The description adds no meaning for depth (presumably tree truncation depth) or targetId, so two of three parameters remain opaque in both schema and prose. This is the main weakness of the definition.

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?

Names a specific resource (accessibility tree snapshot of roles/names) and the exact underlying mechanism (CDP Accessibility.getFullAXTree), which separates it from the heap_snapshot and perf_snapshot siblings that share the 'snapshot' name. It does not explicitly name those siblings as alternatives, but the resource is unambiguous.

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?

'agent-friendly UI map' implies the intended use — building a semantic map of the UI rather than pixels — but there is no explicit when-to-use or when-not-to-use guidance against related tools such as click_ax, assert_ui, or perf_snapshot. Usage must be inferred from the phrase.

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