Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

export_har

Idempotent

Write buffered Electron network requests to a HAR 1.2 JSON file with method, URL, and status, and expose the file as an artifact resource for inspection.

Instructions

Write the buffered network log as HAR 1.2 JSON (method, URL, status; no bodies). Also exposes the file as an artifact resource.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations say readOnlyHint=false and idempotentHint=true; 'Write the buffered network log as HAR 1.2 JSON' is consistent with a non-read-only operation, so no contradiction. It adds useful disclosure beyond the annotations: the output format (HAR 1.2), the excluded content (no bodies), and the artifact-resource side effect — though it never says where the file lands or whether an existing file is overwritten.

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?

Two compact sentences, front-loading the core operation and the artifact side effect. There is no filler, though the parenthetical sits awkwardly in the middle and could be reordered for faster scanning.

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?

No output schema exists, so the description should say more about what the call returns (a path? an artifact handle?) and where the file is written. Naming the artifact resource partially compensates, but for a tool whose main product is a file, the missing destination and return details leave a real gap.

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?

Two parameters at 50% schema coverage: processId is documented in the schema, but 'path' has no description anywhere, and the description does not mention either parameter. It never explains that the HAR is written to the given path or that processId selects which running app is captured, so it fails to 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?

States a specific verb+resource: writing the buffered network log as HAR 1.2 JSON, plus the side effect of exposing it as an artifact resource. The parenthetical '(method, URL, status; no bodies)' pins down what the HAR contains, though it doesn't distinguish itself from any sibling tool by name.

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: the agent can infer 'use this when you want the captured network log as a file', but the description offers no when/when-not conditions and no explicit pointer to a sibling for alternative needs such as clearing or filtering the buffer.

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