Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

block_urls

Blocks specified URL patterns in an Electron app to prevent unwanted network requests, such as analytics calls, during debugging.

Instructions

Block URL patterns via Network.setBlockedURLs (e.g. .analytics.com/)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "urls": "<urls>"
    },
    "name": "block_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesURL patterns to block
targetIdNo
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?

Annotations only declare destructiveHint=false, and the description adds real value beyond that by naming the CDP primitive that backs the call and showing glob pattern syntax. It does not disclose whether the blocklist replaces or appends to existing patterns, whether blocks persist across navigations, or whether the Chrome instance must be in a specific state — meaningful gaps for a network-mutation 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 front-loaded sentence with the verb, resource, mechanism, and an inline example — no filler words or hedging. Optimal density for a simple three-parameter tool.

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?

The tool is simple and the description is sufficient to attempt a call, but it omits the replace-vs-append behavior, targetId's role, and how to revert — details an agent needs to use it safely. With no output schema and partial parameter coverage, slightly more prose would be warranted.

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 67%, with `urls` and `processId` documented in-schema; `targetId` is undocumented in both places. The description's example pattern (*.analytics.com/*) adds format meaning the schema lacks, which is useful but doesn't cover the untargeted parameter.

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?

Specific verb+resource: 'Block URL patterns', with the underlying CDP method (Network.setBlockedURLs) named so a technical agent knows exactly what happens. It does not distinguish itself from nearby siblings such as clear_network_stubs or emulate_network, so it stops 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 Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of the inverse operation (how to unblock/clear the list) despite clear_network_stubs existing in the catalog. The only usage-adjacent content is the example pattern, which is about syntax rather than 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