Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

set_extra_headers

Configure extra HTTP headers for subsequent network requests in an Electron app, enabling custom header injection for debugging and request inspection.

Instructions

Set extra HTTP headers for subsequent requests (Network.setExtraHTTPHeaders)

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": {
      "headers": "<headers>"
    },
    "name": "set_extra_headers"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.9/5.0
Behavior2/5

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

The only annotation is destructiveHint=false, so the description carries the disclosure burden. It does add the useful fact that headers persist into later requests, but says nothing about whether new headers merge with or replace existing ones, how to clear them, or whether the setting is scoped per target/PID.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the persistence clause is well placed. It is tight but arguably too terse given the state-mutating behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a stateful network-mutation tool with a required nested object, three parameters, no output schema, and minimal annotations, the definition is too thin. An agent cannot tell how headers are applied, how to undo them, or how targetId versus processId scope the effect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (only processId is documented), and the description adds no meaning for the required `headers` map — no note on header name casing, multi-value headers, forbidden headers, or what targetId selects. With a nested object parameter, this leaves the key input underspecified.

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?

States a specific verb and resource ("Set extra HTTP headers") and adds the persistence scope "for subsequent requests," plus the underlying CDP method name for traceability. It is clear which sibling family it belongs to (network emulation/stubbing) though it does not name a specific alternative.

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 only implied: an agent can infer it should call this before issuing requests whose headers it wants to control. There is no explicit when-to-use, when-not-to-use, or pointer to siblings like block_urls or clear_network_stubs that also affect outbound requests.

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