Skip to main content
Glama
Sign In
Fast Browser MCP

Fast Browser MCP

by kqlio67
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_get_storage

Inspect and dump all localStorage and sessionStorage items, plus optional CacheStorage, for the current origin to review or debug stored browser data.

Instructions

Inspect and dump all items from localStorage, sessionStorage, and optionally CacheStorage for the current origin.

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

Input Schema

NameRequiredDescriptionDefault
storage_typeNoType of storage to dump: 'all', 'local', 'session', or 'cache'all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / storage_type
      Added value: +{
+  "default": "all",
+  "description": "Type of storage to dump: 'all', 'local', 'session', or 'cache'",
+  "enum": [
+    "all",
+    "local",
+    "session",
+    "cache"
+  ],
+  "type": "string"
+}
  2. First observedv0.8.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It conveys that this is an inspection/dump operation, but does not state whether it is strictly read-only, how large the returned dump may be, whether credentials or sensitive values are included, or what the result format looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It states the action, resources, and scope in one pass.

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 simple one-parameter read tool, the description covers the core operation and parameter scope adequately. However, with no annotations and no output schema, it leaves the return shape and safety profile unstated, which limits completeness.

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 100%, and the sole parameter is a well-documented enum with a default. The description reinforces that CacheStorage is optional, but adds no syntax or semantics beyond what the schema already provides, so the baseline 3 is appropriate.

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 uses specific verbs (inspect, dump) and names the exact resources (localStorage, sessionStorage, CacheStorage) plus scope (current origin). It is clear what the tool does, but it does not explicitly contrast with nearby siblings such as browser_get_cache_storage or browser_clear_storage.

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?

The description implies a read/inspection use case but gives no explicit when-to-use guidance, no exclusions, and no alternatives. An agent must infer on its own when this tool is preferable to sibling storage tools.

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