Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

navigate

Loads an Electron page target at a specified URL and optionally waits for loading to complete, enabling controlled debugging of app pages.

Instructions

Navigate a page target to a URL (Page.navigate) and optionally wait for load

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute or app URL to navigate to
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.
timeoutMsNo
waitUntilLoadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations supply only destructiveHint=false, so the description carries the rest of the burden and does not meet it. It never says that navigation replaces the current page state, what happens on failure or timeout, what the default for waitUntilLoad is, or whether the target must already be attached — all material for a navigation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the primary action comes first and the optional modifier trails it appropriately. Nothing redundant is included.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters, 40% schema coverage, no output schema, and only a single destructiveHint annotation, the description should explain the targetId/processId selection model and timeout behavior. It does neither, leaving an agent to guess on multi-app or multi-target setups.

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 40%: url and processId are documented in the schema, while targetId and timeoutMs have no description at all. The description confirms the url parameter and alludes to waitUntilLoad, but adds no meaning for the undocumented targetId (target vs process distinction) or timeoutMs behavior, so it only partially compensates.

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 gives a specific verb and resource ("Navigate a page target to a URL") and anchors it to the CDP method Page.navigate, so the agent knows exactly what operation this performs. It stops short of distinguishing itself from any sibling, but the purpose is unambiguous on its own.

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 only implied: the mention of "optionally wait for load" hints at a conditional workflow, but there is no statement of when to prefer this over alternatives (e.g. clicking a link, or using a lower-level cdp_command call) and no prerequisites or exclusions called out.

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