Skip to main content
Glama
Sign In
Fast Browser MCP

Fast Browser MCP

by kqlio67
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_new_isolated_tab

Open a new tab in an isolated incognito browser context with zero shared cookies and clean session storage, ensuring privacy and separate sessions.

Instructions

Open a new tab in a fresh, completely isolated browser context (incognito mode: zero shared cookies, clean session storage).

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

Input Schema

NameRequiredDescriptionDefault
urlNoURL to openabout:blank

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.8/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 usefully discloses the isolation profile (no shared cookies, clean session storage), which is real behavioral value. It says nothing about lifecycle, though: whether the isolated context persists after the tab closes, how it is referenced later, or whether it becomes the active tab.

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?

One sentence, front-loaded with the action and immediately qualified by the defining property. No filler and nothing buried.

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 one-parameter, no-output-schema tool, the description covers the essential facts: what it opens and how the context differs. The remaining gap is lifecycle/persistence of the isolated context, which an agent might reasonably wonder about, but it is not critical to invoking the tool.

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% for the single 'url' parameter, including its default of about:blank. The description adds no syntax or format guidance beyond that, so the baseline 3 applies.

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?

States a specific verb (Open) and resource (new tab) and immediately scopes it to a 'fresh, completely isolated browser context', which is precisely what separates it from the sibling browser_new_tab. The parenthetical definition of isolation (zero shared cookies, clean session storage) removes any ambiguity about which tool to pick.

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?

The isolation semantics imply when this tool is appropriate (when you need a clean, cookie-free session), but the description never explicitly says 'use browser_new_tab for a normal tab in the shared context' or names any alternative. Usage must be inferred from the contrast with the sibling name alone.

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