Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

load_storage_state

Restore page cookies, localStorage, and sessionStorage from a saved JSON storage state file or inline payload to rehydrate an Electron app session.

Instructions

Restore page cookies, localStorage, and sessionStorage from a saved JSON storage state file or payload

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

Input Schema

NameRequiredDescriptionDefault
pathNoPath to storage state JSON file
stateNoInline storage state object
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations provide only destructiveHint=false, a low bar the description does meet by describing this as a restore of saved state. However, it does not say whether existing cookies/storage are overwritten or merged, whether the page must be loaded first, or what errors occur if the file is missing — the key behavioral facts for a state-mutating tool. What it does add beyond annotations (which three storage surfaces are covered) is useful but thin.

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 front-loaded sentence that identifies the action and the data surfaces with no filler. It could be tightened slightly by dropping 'page', but nothing is redundant.

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 four-parameter tool with a free-form nested object and no output schema, the definition is minimal: it never describes the structure of the inline state object, the meaning of targetId, or the post-conditions of a restore. An agent can form a call for the common path case but would be guessing on the inline-payload case.

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 description coverage is 75%, so the schema already explains path ('Path to storage state JSON file'), state ('Inline storage state object'), and processId. The description corroborates the file-versus-payload distinction between path and state, adding marginal clarity, but it says nothing about targetId, which is undocumented in both places, nor about the expected shape of the nested state object.

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 gives a specific verb ('Restore') and an exact resource set (page cookies, localStorage, sessionStorage) plus the source (saved JSON storage state file or payload). It implicitly distinguishes itself from the save_storage_state sibling by direction of transfer, though it never names or contrasts an alternative explicitly.

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 guidance on when to use this versus related tools such as set_storage, get_storage, or main_state, and no stated prerequisites (e.g., whether a page must already be attached). The only usage signal is implicit in 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