Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

clear_network_stubs

Disable Fetch interception and remove network stub rules for the current session, restoring normal network behavior.

Instructions

Disable Fetch interception and drop stub rules for this session

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

Input Schema

NameRequiredDescriptionDefault
processIdNoProcess ID. If omitted, uses the single running app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.3/5.0
Behavior3/5

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

The only annotation is destructiveHint=false, so the description carries most of the burden. It usefully discloses that the effect is session-scoped and that both interception and stub rules are removed, but it does not say what happens if no stubs exist, whether it affects in-flight requests, or which process is targeted when processId is omitted.

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?

One short sentence with the action and the session scope front-loaded; there is no filler or redundancy.

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 simple teardown tool with one fully documented parameter and no output schema, the description covers what is removed and the scope, but leaves the operational context (when to invoke it, effect on active pages) unstated.

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?

The single processId parameter is fully documented in the schema (100% coverage), including the default behavior when omitted, so the description adds nothing beyond it. Baseline 3 applies when the schema already does the work.

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 specific verbs and resources: disabling Fetch interception and dropping stub rules, scoped to the session. An agent can tell this is a teardown/reset operation, though it does not explicitly distinguish itself from siblings like network_stub or emulate_network.

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 guidance, no prerequisites, and no mention of alternatives (e.g., when to call this versus overriding an existing stub with network_stub). The agent must infer that this is a cleanup step after stubbing.

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