Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

wait_network_idle

Read-only

Wait until no network request is in flight and activity logs stay quiet for a specified idle interval before continuing Electron debugging.

Instructions

Wait until no network request is in flight and the log has been quiet for idleMs

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a non-mutating, safe call, so the bar is lower. The description usefully clarifies that BOTH conditions (no in-flight request AND a quiet log window) must hold, which is behavior beyond the annotations. It does not say what happens when timeoutMs elapses (error vs. best-effort return), which is the main behavioral unknown for a wait 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 sentence with no filler, and the substantive condition is front-loaded so the agent grasps the wait criterion immediately.

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 four-parameter wait tool with no output schema and only a readOnly annotation, the definition covers the core condition but omits timeout semantics and what the tool returns or raises. Those gaps are not fatal but leave the agent guessing at failure behavior.

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 only 25% — processId is documented in the schema while targetId and timeoutMs are not. The description adds real meaning for idleMs by tying it to 'the log has been quiet for' that duration, but leaves timeoutMs and targetId unelaborated, so it does not fully compensate for the coverage gap.

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 verb ('wait') and a precisely defined condition ('no network request in flight and the log has been quiet for idleMs'), which reads clearly against the generic sibling wait_for. It stops short of naming what the agent should use instead if it only needs a fixed delay, so it is clear but without explicit sibling differentiation.

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 rather than stated: the phrase 'no network request is in flight' hints this belongs after an action that triggers traffic, but there is no explicit when-to-use, when-not-to-use, or pointer to wait_for/act_and_verify as the alternative. An agent must infer the sequencing from context.

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