Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

capture_mhtml

Idempotent

Saves an Electron page as an MHTML snapshot using Page.captureSnapshot and registers the resulting file as an artifact resource for later inspection.

Instructions

Save page as MHTML via Page.captureSnapshot. Also registers 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": "capture_mhtml"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
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
Behavior3/5

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

Annotations only declare readOnlyHint=false and idempotentHint=true; the description adds real value by disclosing a side effect beyond file writing, namely that the file is registered as an artifact resource. It still omits where the file lands when no path is given and whether an existing file is overwritten, despite idempotentHint implying overwrite semantics.

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 tight sentences with the main action front-loaded and the artifact side effect second; no filler. It is arguably too terse for the parameter set, but nothing written is wasted.

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?

With three parameters, a 33% schema coverage, and no output schema, the description should say what the call returns (file path, artifact ID or handle) and what happens when path/targetId are omitted. Neither is covered, so an agent cannot predict the result of a successful call.

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 carries a description. The description says nothing about path or targetId, so it fails to compensate for the two undocumented parameters, leaving the agent to guess where output is written.

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 ("Save page as MHTML") and even names the underlying mechanism (Page.captureSnapshot). It does not distinguish itself from the adjacent export_har sibling, but the purpose is unambiguous from the first clause.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as export_har or diff_screenshot. The agent must infer the selection context from the name alone.

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