Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

network_failure_report

Idempotent

Gather failed HTTP requests, capture their response bodies, and export a HAR artifact to diagnose Electron app network failures.

Instructions

Composite network diagnostics: gathers all failed HTTP requests (status >= 400 or failed requests), fetches response bodies inline, and exports a HAR artifact.

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

Input Schema

NameRequiredDescriptionDefault
tailNoOptional limit of recent failures to return
harPathNoOptional path for the exported HAR file
processIdNoProcess ID. If omitted, uses the single running app.
urlPatternNoOptional URL substring or pattern filter
exportHarFileNoWhether to export a HAR file (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations mark readOnlyHint=false and idempotentHint=true; the description usefully explains why the false readOnly carries meaning by disclosing that a HAR artifact is written out. It also notes that response bodies are fetched inline, which signals a heavier operation than a simple listing. It stops short of stating size limits, cost, or whether it clears the existing buffer, but adds real value beyond the annotations.

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 a colon-delimited enumeration of the three stages. Every clause carries information and nothing is repeated from the schema or annotations.

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 five-parameter, zero-required tool with no output schema, the description covers the full behavior pipeline and the main side effect. Missing only peripheral detail such as return shape of the inlined bodies and interaction with existing captured buffers, which are minor gaps against full schema coverage.

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 coverage is 100%, so parameters like tail, harPath, processId, urlPattern and exportHarFile are already fully documented in the schema. The description adds the failure definition (status >= 400) which sharpens the filtering semantics but says nothing about the tail limit, processId scoping, or how urlPattern interacts with the failure filter. Baseline 3 is appropriate.

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?

Uses a specific verb chain against a specific resource: gather failed HTTP requests, fetch response bodies inline, export a HAR artifact. This clearly distinguishes it from a plain log reader like get_network_log or a pure export_har sibling. The one gap is that it does not name which sibling to use when the agent only needs raw export, but the composite scope is still self-evident.

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?

The word 'diagnostics' plus 'all failed HTTP requests' implies this is the tool to reach for when investigating network failures rather than general traffic inspection. However, there is no explicit when-to-use/when-not statement and no pointer to alternatives such as get_network_log for successful traffic or export_har for a HAR of everything. Usage is inferable but not spelled 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