Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_network_log

Read-only

Retrieve buffered network request and response events captured via CDP, with optional filters for tail, HTTP status, failed requests, and URL patterns.

Instructions

Get buffered network request/response events captured via CDP Network domain. Supports optional filtering by tail, status code, failure status, or URL pattern.

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

Input Schema

NameRequiredDescriptionDefault
tailNo
statusNoOptional HTTP status filter (e.g. 404, 500)
processIdNoProcess ID. If omitted, uses the single running app.
failedOnlyNoIf true, only return requests that failed or responded with status >= 400
urlPatternNoOptional URL substring or glob filter

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?

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds meaningful context by revealing that results come from a buffer populated via the CDP Network domain, implying the data is bounded and only present if capture occurred, but it never says whether the buffer can overflow, whether capture must be enabled first, or whether bodies are included.

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 compact sentences, front-loaded with the resource and followed by capabilities. Every clause carries information and nothing is redundant.

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?

There is no output schema, so the description bears responsibility for describing return shape, yet 'request/response events' does not say whether bodies, headers, or timing are included (the existence of a separate get_response_body sibling hints bodies are excluded). Complete enough to call correctly, but thin for a 5-parameter diagnostic tool with no return documentation.

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 80%, so the schema itself documents status, processId, failedOnly, and urlPattern, making 3 the baseline. The description only restates the filter categories already present in the schema and omits processId entirely, adding no format or precedence detail (e.g. how tail interacts with the other filters).

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 states a specific verb and resource ('Get buffered network request/response events') and adds the capture mechanism ('via CDP Network domain'), which cleanly separates it from logging siblings like get_ipc_log or get_console_messages. It stops short of naming any sibling or stating scope limits explicitly, so it falls just short of a 5.

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 by 'buffered' and by the list of filters, but there is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as network_failure_report, wait_network_idle, get_response_body, or clear_buffers. For a diagnostic tool with many overlapping siblings, this leaves the agent to infer selection.

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