Skip to main content
Glama
Sign In
Fast Browser MCP

Fast Browser MCP

by kqlio67
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_clear_storage

Clear browser cache and cookies to remove stored site data, fix stale sessions, or reset login state.

Instructions

Clear browser cache and/or cookies.

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_clear_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
clear_cacheNo
clear_cookiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the destructive targets (cache and cookies), which is the key effect an agent needs, but omits scope (per-tab vs global), reversibility, session-logout implications, and whether a reload occurs.

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 short sentence that front-loads the action and its targets. It is efficient, though it is arguably under-specified rather than genuinely tight.

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?

For a destructive tool with no annotations, no output schema, and zero parameter description coverage, the definition is too thin. An agent lacks information about scope, side effects on the active session, and the semantics of the two flags.

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 0% for both booleans, so the schema adds no meaning. The description's "cache and/or cookies" phrasing does map onto clear_cache and clear_cookies and implies they are independently combinable, but it never explains the default-true behavior or what passing only one flag does.

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 ("Clear") and resource ("browser cache and/or cookies"), which an agent can immediately distinguish from the read-oriented siblings like browser_get_storage or browser_get_cookies. It does not explicitly name a sibling or scope, but the action is unambiguous.

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 guidance on when to use this tool versus alternatives such as browser_set_cookie or browser_get_storage, nor any prerequisites or exclusions. The agent must infer all usage context.

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