Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

virtual_clock

Pause or advance virtual time in Electron debugging, including granting a time budget when advancing, to control timers and async execution during tests.

Instructions

Emulation.setVirtualTimePolicy — pause / advance virtual time (use budget when advancing)

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": {
      "policy": "<policy>"
    },
    "name": "virtual_clock"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetNoVirtual ms to grant when advancing
policyYes
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.2/5.0
Behavior2/5

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

Annotations supply only destructiveHint=false, so the description carries nearly the full behavioral burden and does not meet it. It never says what pausing does to the running app (frozen timers, stalled network fetches), whether the policy persists after the call, or what happens when the granted budget is exhausted. The single clause about budget is the only added context.

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 that front-loads the method name and the action, with the conditional hint bracketed at the end. Nothing is wasted, though the telegraphic slash construction is slightly harder to parse than a plain clause.

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 parameters, half the schema undocumented, no output schema, and only a destructiveHint annotation, the definition should explain the consequences of each policy value and the effect on the target process. It supplies almost none of that, leaving an agent unable to predict the state change it is triggering.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, so the description must compensate somewhat, and 'use budget when advancing' does explain the coupling between the budget parameter and the advance policy, which the schema itself does not state. The undocumented targetId remains unexplained, keeping this short of a top score.

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 the underlying CDP method and states the resource (virtual time) with the two key actions (pause / advance), so it is more than a restatement of the name. It is not differentiated from siblings such as pause or emulate, which an agent could plausibly confuse with this, but the verb+resource pairing is unambiguous on its own.

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?

The parenthetical 'use budget when advancing' is a real conditional hint tying one parameter to one policy, which is more than nothing. However, there is no guidance on when to choose this over the sibling pause tool, when pauseIfNetworkFetchesPending is appropriate, or what preconditions must hold before changing virtual time policy.

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