Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

emulate_network

Set a page offline or simulate slow network conditions with added latency and upload/download throughput limits; use clear to restore normal networking.

Instructions

Set the page offline, or slow it with latency and throughput in bytes per second. clear:true restores a normal network. Does not change viewport, user agent, geolocation, or media; use emulate for those.

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

Input Schema

NameRequiredDescriptionDefault
clearNo
offlineNotrue makes navigator.onLine false and fails fetches
targetIdNo
latencyMsNoAdded round-trip latency in milliseconds
processIdNoProcess ID. If omitted, uses the single running app.
uploadThroughputNoMax upload bytes/sec. -1 means unlimited
downloadThroughputNoMax download bytes/sec. -1 means unlimited

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare destructiveHint=false, so the description carries most of the burden and does add real scope information: the effect is per-page and scoped to network conditions only, with an explicit list of untouched surfaces. It stops short of stating persistence behavior (does the throttle survive navigation?) or whether clear is required before re-applying settings.

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?

Two sentences, front-loaded with the primary capability, followed immediately by the reset instruction and the negative scope. No filler or restatement of the tool name.

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 7-parameter, all-optional mutation tool with no output schema, the definition covers purpose, reset semantics, units, and exclusions. What is missing is lifecycle information — how long emulation persists and whether it must be cleared when switching targets or processes.

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 71%, and the description fills the two gaps that matter: what clear:true does and that latency/throughput are the throttling knobs, with throughput explicitly in bytes per second. It does not address targetId, but the description's 'page' framing plus the schema's remaining descriptions leave that workable.

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?

States a concrete verb and resource: 'Set the page offline, or slow it with latency and throughput in bytes per second', plus the reset path via clear:true. It also explicitly carves out what it does not do (viewport, user agent, geolocation, media), which separates it from the sibling emulate tool.

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

Usage Guidelines5/5

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

Gives the positive cases (go offline, add latency/limit throughput) and the exit case (clear:true restores a normal network). It also names the correct alternative for non-network emulation ('use emulate for those'), so an agent can route without guessing.

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