Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

run_script

Executes ordered Electron debugging steps with variables, conditional branches, assertions, retries, and failure screenshots; optionally exports recorded workflows as Playwright tests.

Instructions

Advanced server-side step runner & workflow engine: executes an array of tool steps sequentially with templating ({{vars.x}}, {{steps[0].result.x}}, {{secret:KEY}}), conditional branching (if), assertions (expect), automatic retries, diagnostic failure screenshots, and optional export to Playwright test specs.

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

Input Schema

NameRequiredDescriptionDefault
scriptYesArray of steps or path/JSON string to execute
exportAsNoExport the executed steps as executable Playwright test code or JSON recipe
processIdNoTarget process ID. If omitted, uses the single running app.
variablesNoInitial variables map for {{vars.name}} interpolation
exportPathNoOptional file path on disk to save the exported test or JSON recipe
stopOnFirstErrorNoWhether to halt script execution upon first step failure (default: true)
captureFailureArtifactsNoWhether to automatically capture screenshot artifacts and diagnostic logs on step failure (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.8/5.0
Behavior4/5

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

With only destructiveHint=false supplied, the description adds substantial behavioral context: sequential execution, templating syntax, branching, assertions, retries, failure screenshots, and Playwright export. It still omits what the workflow returns, permission/security implications of {{secret:KEY}}, and the risk that invoked steps may themselves mutate state.

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 enumerates the main features without filler, though the dense feature list and 'Advanced' framing make it slightly harder to scan. It earns its length for a complex workflow tool.

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 seven-parameter nested-object workflow engine with no output schema and minimal annotations, the description covers major capabilities but leaves return values, process targeting, and failure/error output shape unexplained. The rich input schema offsets some gaps, but not all.

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 100%, so the baseline is 3; the description reinforces templating and export concepts but adds few parameter-level details beyond the schema. It does not clarify processId targeting, stopOnFirstError interaction with onError, or exportPath behavior.

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?

The description names a specific verb-resource ('executes an array of tool steps sequentially') and scope ('server-side step runner & workflow engine'), covering orchestration rather than a single action. An agent can distinguish it from single-action siblings like click or assert_ui without opening the schema.

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 capability list implies this tool is for multi-step workflows needing templating, branching, retries, assertions, or export, but it never states when to prefer it over act_and_verify or individual tools, nor any exclusions. Guidance is inferred rather than explicit.

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