Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

network_stub

Intercept matching URLs through Fetch to fulfill or fail requests, replacing existing rules with the same URL pattern. Use with clear_network_stubs to remove stubs.

Instructions

Intercept matching URLs via Fetch and fulfill or fail them. Replaces a rule with the same urlPattern. Pair with clear_network_stubs.

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": {
      "urlPattern": "<urlPattern>",
      "action": "<action>"
    },
    "name": "network_stub"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
actionYes
statusNo
headersNo
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.
urlPatternYesCDP urlPattern; * is a wildcard, e.g. "*api/users*"
contentTypeNo
errorReasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only supply destructiveHint=false, so the description carries most of the burden. It usefully discloses that an existing rule with the same urlPattern is replaced and that interception runs through the Fetch domain, plus the cleanup pairing — meaningful behavior beyond the annotation, though it omits whether stubs persist across navigations or whether requests stall until fulfilled.

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?

Three short sentences, front-loaded with the core action, followed by the overwrite caveat and the cleanup pairing. No filler and nothing buried.

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 9-parameter mutation-adjacent tool with no output schema and thin annotations, the description covers purpose and replacement behavior but leaves the parameter-to-action wiring and stub persistence unexplained. Adequate to start, not sufficient to avoid a mis-call on the conditional fields.

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

Parameters2/5

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

Schema description coverage is only 22% with 9 parameters, so the description must compensate and largely does not. It never explains that body/status/headers/contentType apply to action=fulfill and errorReason applies to action=fail, which is the single most important semantic distinction for calling this tool correctly.

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 — intercept matching URLs via Fetch and fulfill or fail them — so the agent knows this installs a network stub rather than reading logs (get_network_log) or blocking (block_urls). It does not explicitly distinguish itself from emulate_network, but the fulfill/fail framing is concrete enough to select on.

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?

"Pair with clear_network_stubs" gives useful lifecycle guidance (set up here, tear down there), and "Replaces a rule with the same urlPattern" implies repeat calls are idempotent. However, there is no explicit when-to-use-this-vs-emulate_network/block_urls guidance, leaving the choice partly to inference.

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