Skip to main content
Glama
Sign In
nstbrowser-playwright-mcp

nstbrowser-playwright-mcp

by jackie099
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

switch_session

Switch the active browser session by providing a session ID, directing Playwright automation to the desired NSTBrowser profile.

Instructions

Switch the active browser session

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": {
      "sessionId": "<sessionId>"
    },
    "name": "switch_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesSession ID to switch to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the basic action without revealing whether the session ID must exist, whether the previous session is deactivated or remains available, or any side effects. This is insufficient for a state-changing tool.

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?

The description is a single concise sentence, 'Switch the active browser session', with no filler or redundant information. It is immediately understandable and efficiently conveys the core purpose.

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?

For a simple one-parameter tool, the description is minimally adequate, but it lacks important context about prerequisites (e.g., session must exist) and consequences (e.g., affects subsequent calls). With no annotations or output schema, more context would be beneficial.

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?

The input schema already provides a clear description for sessionId: 'Session ID to switch to', and schema coverage is 100%. The tool description adds no additional parameter-level detail, but since the schema covers it fully, this is acceptable.

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 'Switch the active browser session' clearly identifies the action (switch) and the target resource (active browser session). It distinguishes implicitly from siblings like create_session and close_session by focusing on changing state rather than creating or destroying, though it could be more explicit about its unique role.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites such as listing sessions first, nor does it explain that switching affects subsequent operations. There are no explicit when-to-use or when-not-to-use instructions.

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