Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_downloads

Arms download capture to suppress save dialogs, record files saved by an Electron app, and list saved paths; call before downloads start and again to retrieve savePath.

Instructions

Arm download capture and list files saved by the app. Requires inspectMain. The first call installs a will-download listener that writes into directory (default: OS temp) and suppresses the save dialog. Call it before the download starts, then call again for savePath.

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

Input Schema

NameRequiredDescriptionDefault
urlNoOptional URL to start downloading on the app session after the listener is armed
directoryNoDirectory for saved files. Used when the listener is first armed.
processIdNoProcess ID. If omitted, uses the single running app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare destructiveHint=false, so the description carries the behavioral load and does so well: it discloses that the first call installs a will-download listener, writes files into a directory defaulting to OS temp, and suppresses the save dialog (a real side effect the agent must know about). It also surfaces the inspectMain authorization requirement and the two-call pattern.

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?

Four short sentences, front-loaded with purpose, then prerequisite, then mechanism, then call sequence — no filler. The closing "then call again for savePath" is slightly telegraphic, but nothing is wasted.

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 3-param tool with no output schema and a notable side effect (suppressing the save dialog), the description covers purpose, prerequisite, defaults, and call ordering. It does not describe what the listing returns (names vs. full paths) or mention processId, leaving minor gaps.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: the OS-temp default for directory and the fact that directory only takes effect when the listener is first armed, plus url triggering a download after arming. Only processId is left to the schema alone.

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?

"Arm download capture and list files saved by the app" gives a specific verb+resource plus the unusual two-phase mechanism (arm listener, then list). Even without naming a sibling, the arming behavior makes it unmistakable which tool this is among the surrounding get_* readers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sequencing advice — "Call it before the download starts, then call again for savePath" — plus the prerequisite "Requires inspectMain" tell the agent exactly when to reach for it. It stops short of naming alternatives or stating when not to use it, so it lands at 4 rather than 5.

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