Skip to main content
Glama

browser_reset

Reset the MCP client's JavaScript runtime and variables to clear stale state without closing tabs. Use it when browser actions misbehave and need a clean script context.

Instructions

Reset this MCP client's JavaScript runtime and variables. Does not close tabs. In-progress browser actions may still finish.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 burden; it does disclose two real traits: tabs stay open and in-flight actions may still complete. It does not say what else survives or is cleared (localStorage, cookies, session state, page URL), which is exactly what an agent needs before resetting.

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?

Three short sentences, front-loaded with the action and its scope, followed by the two constraints that matter. Nothing is wasted or padded.

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?

For a zero-parameter tool with no output schema and no annotations, the description covers the essentials: what resets, what is preserved, and the async caveat. The only shortfall is that the boundary of "runtime and variables" against persistent storage is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly presents this as an argument-free operation.

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?

States a specific verb plus a precise resource: "Reset this MCP client's JavaScript runtime and variables." The clause "Does not close tabs" implicitly separates it from browser_close and browser_reload without naming them, so an agent can place it, though no sibling is called out by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied — an agent must infer that it should call this when JS state or variables are polluted but the tab should survive. The exclusion ("does not close tabs") narrows the case usefully, but there is no explicit when-to-use versus browser_reload or browser_close.

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