Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

open_deep_link

Delivers a deep link to a running Electron app by emitting open-url and second-instance events, then returns the recorded URL and mirrors it to window.DEEP_LINK.

Instructions

Emit Electron open-url and second-instance (requires inspectMain). Returns the URL the app recorded and mirrors it to window.DEEP_LINK.

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

Input Schema

NameRequiredDescriptionDefault
urlYesDeep link or URL to deliver
channelNoAlso webContents.send(channel, url) when set
processIdNoProcess ID. If omitted, uses the single running app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the sparse destructiveHint=false annotation, the description discloses the actual side effects: it emits two specific Electron events, writes the URL to a global (window.__DEEP_LINK__), and depends on inspectMain being enabled. That is real behavioral context an agent would otherwise not have from the schema.

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?

Two tight sentences with the mechanism and prerequisite front-loaded and the return behavior second. No filler, though the dense technical shorthand makes it readable mainly to someone already familiar with the Electron concepts.

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?

There is no output schema, and the description covers the return value and the mirrored global, plus the inspectMain prerequisite, for a simple 3-parameter tool. Only the optional channel/processId behaviors are left to the schema, which handles them at full coverage.

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 url, channel, and processId are already documented in the schema. The description adds only that the URL is what the app 'recorded' and re-mirrored; it says nothing extra about the optional channel or processId parameters, so baseline 3 applies.

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?

The description names a specific action (emitting Electron's open-url and second-instance events) and the resource it targets, and it explicitly states the return value (the recorded URL, mirrored to window.__DEEP_LINK__). It is recognizable as the deep-link delivery tool, though the jargon (open-url, second-instance) assumes Electron familiarity and it does not name a sibling to contrast with.

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?

Usage is implied by the mechanism described — use this to deliver a deep link or URL to a running Electron app — and the prerequisite 'requires inspectMain' is stated. There is no explicit when-not guidance or named alternative for cases where inspectMain is unavailable, so the agent must infer the boundary itself.

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