Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

set_storage

Writes localStorage or sessionStorage entries for an Electron app, with an option to clear existing storage first.

Instructions

Write localStorage or sessionStorage entries (optionally clear first)

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": {
      "entries": "<entries>"
    },
    "name": "set_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
clearNo
entriesYes
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.1/5.0
Behavior3/5

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

The single annotation only declares destructiveHint=false, so the description carries most of the behavioral burden. It usefully discloses that entries are written and that existing storage can be wiped first when the clear flag is set, which is real context beyond the annotation, but it says nothing about overwrite semantics for existing keys, persistence across reloads, or error behavior when the page context is missing. Note the tension: the opt-in clear path is data-destroying while destructiveHint is false, so the description is the only warning an agent gets.

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 with the action front-loaded and no filler. It is efficient, though the terseness leaves the parenthetical doing more explanatory work than a single clause can support.

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 five parameters, a nested object payload, no output schema, and only 20% schema description coverage, the definition should explain the entries key/value shape and how targetId/processId select the app. It omits both, leaving the agent to infer the most error-prone parts of the call from the raw schema.

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 low (20%), so the description needs to compensate, and it only partially does: it accounts for 'entries', 'kind' (localStorage vs sessionStorage), and the 'clear' flag. It adds nothing about 'targetId' or 'processId', nor about the fact that entry values must be strings per the nested additionalProperties schema.

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 ('Write') and resource ('localStorage or sessionStorage entries'), so the agent knows exactly what the tool mutates and which storage kinds are covered. It does not name the read counterpart (get_storage) explicitly, but the write/read split is self-evident from the verb.

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 alternatives, nor any mention of prerequisites such as the target page needing to be loaded. The only hint is the parenthetical 'optionally clear first', which implies an ordering choice but does not say when that option is appropriate.

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