Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

reload

Refresh a page target or all page targets in an Electron app, optionally ignoring cache and targeting a specific process ID.

Instructions

Reload a page target (or all page targets) in an Electron app

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

Input Schema

NameRequiredDescriptionDefault
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.
ignoreCacheNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

C2.9/5.0
Behavior2/5

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

The only annotation is destructiveHint=false, so the description carries the behavioral burden and largely fails it: it never says that reloading discards in-page state (form input, JS variables, scroll), whether it waits for load completion, or what ignoreCache does. 'Reload' alone does not tell an agent whether this is safe mid-workflow.

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 well-formed sentence with the scope condition front-loaded in the parenthetical. It is efficient, but the brevity is partly under-specification rather than disciplined concision.

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 3-parameter mutation-adjacent action with no output schema and near-zero annotation coverage, one sentence is not enough. An agent still cannot tell what 'all page targets' means across windows/processes, what state is lost, or what the cache flag changes.

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 coverage is only 33% (only processId is documented). The description does clarify that targetId is optional by saying 'or all page targets', but it adds nothing for ignoreCache and nothing about how targetId and processId interact. Below the baseline because coverage is low and the description only partly compensates.

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 ('Reload') and resource ('a page target (or all page targets) in an Electron app'), so an agent immediately knows the operation. It does not name or contrast with any sibling, so it stops short of 5.

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 '(or all page targets)' implies the omitted-target case, giving implicit guidance on when to pass a targetId. There is no explicit when-to-use/when-not, no prerequisites, and no mention of how this relates to alternatives such as emulate or navigate-style siblings.

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