Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

repro_bundle

Read-only

Package a complete repro investigation bundle into a zip artifact, including screenshot, MHTML DOM archive, HAR network replay, source-mapped stack traces, logs, and system health info.

Instructions

Package a complete, self-contained repro investigation bundle (screenshot, MHTML DOM archive, HAR network replay, source-mapped stack traces, logs, and system/health info) into a zip artifact.

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

Input Schema

NameRequiredDescriptionDefault
notesNoOptional bug reproduction steps or user notes to include in report
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.
outputPathNoOptional destination zip file path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation covers the safety profile of the target application, so the description is not the sole source of that information. The description adds real value by disclosing the breadth of data collected, but leaves key behavioral questions open: whether it triggers fresh captures or packages already-collected buffers, where the zip lands when outputPath is omitted, and whether capture buffers are consumed or cleared as a side effect.

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 a parenthetical enumeration that earns its length by specifying what the bundle contains. No filler or restatement of the name, though the parenthetical list is dense enough that it could be split for scanability.

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?

With only a readOnlyHint annotation, no output schema, and four parameters, the description covers the 'what gets captured' half well. It omits the operational half an agent needs: default output location, whether an app must already be attached or discovered first, and whether the operation is expensive or long-running.

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 coverage is 75%, just under the threshold where the schema alone would justify a neutral score, and the description says nothing about any of the four parameters. In particular targetId carries no description in the schema and receives no explanation here, so the one undocumented parameter stays unexplained in both places.

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 resource ('Package a complete, self-contained repro investigation bundle ... into a zip artifact') and enumerates the payload contents (screenshot, MHTML, HAR, source-mapped stack traces, logs, system/health info), which is far more informative than the tool name alone. It does not, however, distinguish itself from sibling capture tools like screenshot, capture_mhtml, or export_har, which produce subsets of the same artifacts.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. An agent must infer that this is the bundled counterpart to the individual capture siblings; nothing in the text says to prefer this over calling screenshot + capture_mhtml + export_har separately, or in what situations one would do so.

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