Skip to main content
Glama
yfe404

proxy-mcp

by yfe404
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

interceptor_browser_get_storage_value

Retrieve a specific localStorage or sessionStorage value by item ID to inspect or debug browser storage. Provide target, storage type, and item ID to get the stored value.

Instructions

Get one localStorage/sessionStorage value by item_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originNoOptional origin override (must match current page origin)
item_idYesitem_id from interceptor_browser_list_storage_keys
target_idYesTarget ID from interceptor_browser_launch
storage_typeYesStorage type
value_max_charsNoMax characters for returned value (default: 20000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.3
    • changedInput schema / properties / target_id / description
      Previous value: -"Target ID from interceptor_browser_launch or interceptor_camoufox_launch"New value: +"Target ID from interceptor_browser_launch"
  2. Changed1 schema field changedv3.3.1
    • changedInput schema / properties / target_id / description
      Previous value: -"Target ID from interceptor_browser_launch"New value: +"Target ID from interceptor_browser_launch or interceptor_camoufox_launch"
  3. Addedv2.3.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as whether the tool returns null for missing keys, errors on invalid storage type, or has side effects. With no annotations, the description carries the full burden but offers minimal transparency.

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 that conveys the core action efficiently. No redundant words or filler. Every word contributes meaning.

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?

Given 5 parameters and no output schema, the description is minimally adequate. It explains the resource and key parameter but omits return format, error conditions, or handling of optional parameters like origin or value_max_chars. Overall, functional but leaves room for exploration.

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%, so baseline is 3. The description adds no extra meaning beyond the schema; it only reiterates the item_id parameter. No parameter format, constraints, or dependencies are clarified beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies the verb 'Get', the resource 'one localStorage/sessionStorage value', and the key parameter 'item_id'. It distinguishes this tool from siblings like 'interceptor_browser_list_storage_keys' which lists keys rather than values.

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?

No guidance on when to use this tool versus alternatives (e.g., when needing all keys or bulk values). No mention of prerequisites like a launched browser or storage context. The description lacks contextual cues for appropriate invocation.

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