Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

get_storage

Read-only

Read localStorage or sessionStorage key/value pairs from an Electron page to inspect persisted state, optionally targeting a specific process ID when multiple apps run.

Instructions

Read localStorage or sessionStorage key/value pairs from the page

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

Input Schema

NameRequiredDescriptionDefault
kindNo
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?

The readOnlyHint annotation already establishes this is a safe read; the description adds only that the data comes from the live page and covers both storage kinds. It says nothing about requiring an attached page/target, what happens when a key is absent, or the shape of the returned map.

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 and the resource stated before the qualifier. It is arguably too terse for a three-parameter tool, but nothing in it is wasted.

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?

The description says what is returned at a high level (key/value pairs), which is useful given there is no output schema. However, with three parameters (two undocumented) and no stated prerequisite of an attached page or target, an agent could easily call it without the necessary context.

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 description coverage is only 33%, so the description should compensate, but it adds nothing beyond the schema. Its mention of localStorage/sessionStorage merely restates the 'kind' enum, and targetId is left completely undocumented in both places.

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 clear verb ('Read') plus the exact resources ('localStorage or sessionStorage key/value pairs') and scope ('from the page'). That distinguishes it from the write-side siblings set_storage/save_storage_state, though it never names them explicitly.

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?

Usage is only implied: 'from the page' suggests reading live browser storage rather than loading a persisted state file, which hints at the boundary with load_storage_state. There is no explicit when-to-use, when-not-to-use, or alternative named.

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