Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_mock_calls

Read-only

Retrieve recorded invocations and arguments for a mocked Electron API method to verify calls and inspect test behavior.

Instructions

Get recorded invocations and arguments for a mocked Electron API method

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": {
      "module": "<module>",
      "method": "<method>"
    },
    "name": "get_mock_calls"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodYesMethod name
moduleYesElectron module name
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.3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the bar is lower. The description adds that the result contains both invocation records and their arguments, which is useful. It says nothing about ordering, completeness across processes, or what is returned when nothing was recorded.

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

Conciseness5/5

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

A single front-loaded sentence with the key noun ('recorded invocations and arguments') placed early and zero filler. Nothing could be removed without losing information.

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?

For a simple read-only getter with no output schema, the description covers what the tool fetches but not the shape of the result or the empty-state behavior, and it does not explain the processId/targetId scoping. Adequate to invoke correctly, thin for interpreting results.

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%, near the high band, and the two required parameters (module, method) are documented in the schema. The description adds no meaning for module/method/processId and leaves targetId entirely undocumented in both places, but the required inputs are self-explanatory.

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 specific verb plus resource: retrieving recorded invocations and their arguments for a mocked Electron API method. That is clearly distinguishable from the setup-oriented sibling mock_electron_api. It stops short of explicitly naming that sibling, so a 4 rather than a 5.

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: nothing states that the method must already be mocked via mock_electron_api, no mention of what to do when no calls are recorded, and no pointer to clear_buffers for resetting recordings. Usage is only inferable from the name and the word 'recorded'.

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