Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

diff_screenshot

Read-only

Capture a screenshot or compare an existing PNG against a baseline, reporting whether images are identical and their byte similarity.

Instructions

Capture (or compare) a screenshot against a baseline PNG; reports identical + byte similarity

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": {
      "baselinePath": "<baselinePath>"
    },
    "name": "diff_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorNo
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.
currentPathNoExisting PNG to compare; if omitted, captures fresh
baselinePathYes

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 declare readOnlyHint=true, so safety is already covered. The description adds genuine behavioral value by disclosing what the result contains ('identical + byte similarity'), which is important since there is no output schema, but it omits whether anything is written to disk and how the baseline is used or updated.

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?

One compact sentence with the action front-loaded and the output fields after the semicolon; nothing is padded. It is arguably too terse given the two operating modes, but there is no wasted wording.

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 5-parameter tool with no output schema and low schema coverage, the description leaves key questions unanswered: what selector and targetId scope, what happens when currentPath is supplied, and whether a capture is persisted. The brief return-value note is not enough to make the definition self-sufficient.

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?

With 5 parameters and only 40% schema description coverage, the description needs to compensate and largely does not. It never explains baselinePath (the required parameter), selector, or targetId, and only implicitly gestures at currentPath via the word 'compare' — information the schema already gives more precisely.

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 names a concrete verb pair (capture or compare) and resource (screenshot against a baseline PNG), so an agent knows roughly what it does. However, it does not differentiate itself from the sibling tools 'screenshot' and 'save_screenshot', leaving the agent to guess which capture path to pick.

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 explicit when-to-use or when-not-to-use guidance. The parenthetical '(or compare)' hints at a mode but never states the condition that selects comparison versus fresh capture, nor when to prefer this over the plain 'screenshot' sibling.

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