Skip to main content
Glama
mcp-browserdata

mcp-browserdata

by igortetyuev

get_site_storage

Reads localStorage and optional sessionStorage for a given browser origin, with values masked unless you set reveal to true. Use it to inspect stored site data per domain.

Instructions

localStorage (+sessionStorage) for one origin, e.g. "https://example.com". Values masked unless reveal=True.

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": {
      "browser": "<browser>",
      "origin": "<origin>"
    },
    "name": "get_site_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYes
revealNo
browserYes
include_sessionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two meaningful traits: values are masked by default and session storage is only included on request, which matters for a tool returning potentially sensitive data. It says nothing about response size, per-origin limits, or what happens for an origin with no stored data.

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?

Two tight sentences with the resource and scope front-loaded and the masking caveat following. The '+sessionStorage' parenthetical is slightly compressed and takes a moment to parse, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. For a four-parameter read tool, the description covers the sensitive-data behavior and most parameters; only the browser parameter and any multi-browser behavior are left unaddressed.

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 coverage is 0%, so the description must compensate. It clarifies origin via a concrete URL example, ties reveal to unmasking, and the '+sessionStorage' parenthetical implies include_session opt-in. The browser parameter is never mentioned, leaving one of four parameters with no explanation anywhere.

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?

Names a specific resource (localStorage plus optional sessionStorage) scoped to a single origin, which is enough to separate it from get_cookies or get_credentials. The read verb itself is only implied by the tool name, not stated in the description.

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 statement of when to use this versus the sibling getters, nor any prerequisite or exclusion. The only guidance-like content is the reveal=True hint, which is parameter behavior rather than usage routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.