Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

restore_electron_mocks

Restore original implementations of mocked Electron APIs to undo test or debug mocks, with optional targeting by module, method, process, or app.

Instructions

Restore original implementations of mocked Electron APIs

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

Input Schema

NameRequiredDescriptionDefault
methodNoMethod to restore (omit to restore all in module)
moduleNoModule to restore (omit to restore all)
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.1/5.0
Behavior3/5

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

The annotations supply only destructiveHint=false, so the description carries most of the burden. It does add real behavioral content by saying the original implementations are put back, which clarifies the effect beyond a generic 'reset.' However, it omits what happens when nothing is mocked, whether the operation is idempotent, and whether restoring is scoped per process or app.

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 or repetition. It is efficient, though the brevity borders on under-specification for a tool with four parameters.

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 four optional parameters, one undocumented (targetId), no output schema, and only a single annotation hint, the description should explain scoping semantics such as restoring all versus a single method. As written, an agent cannot tell from the description alone what targetId means or how partial restores behave.

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 75%, with method, module, and processId documented and targetId left bare. The description adds no parameter-level meaning at all, so it neither compensates for the undocumented targetId nor clarifies how method/module interact. At this coverage level the schema does most of the work, making a 3 the appropriate baseline.

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 states a specific verb and resource: 'Restore original implementations of mocked Electron APIs.' That is unambiguous and, by implication, the inverse of the mock-creating sibling. It stops short of naming the counterpart tool explicitly, so the differentiation is inferred rather than stated.

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 or when-not-to-use guidance, no mention of prerequisites such as a mock needing to exist first, and no reference to an alternative tool. The only usage signal is the implicit 'undo mocking' framing carried by the word 'restore.'

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