Skip to main content
Glama

Disconnect from a browser

disconnect_browser

Disconnect this control session from a browser. The browser keeps running; use close_browser to stop it.

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": "disconnect_browser"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesSession ID of the browser to disconnect

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only but non-destructive operation. The description adds useful context beyond that: disconnecting only ends the control session, while the browser process continues running. It does not explain reconnection behavior or return details, but for this simple operation the added context is substantial.

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?

Two short sentences with no wasted wording. The core operation is front-loaded, followed immediately by the key behavioral distinction and alternative tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter disconnect tool with complete schema coverage and annotations covering safety, the description supplies what an agent needs: what it does, that the browser survives, and when to choose close_browser instead.

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 coverage is 100% and the sole parameter already has a schema description ('Session ID of the browser to disconnect'). The tool description does not add further parameter semantics such as format or source, so the baseline score is appropriate.

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 states a specific verb and resource: 'Disconnect this control session from a browser.' It also immediately distinguishes the operation from close_browser by clarifying that the browser keeps running.

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

Usage Guidelines5/5

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

It explicitly names the alternative, close_browser, and states the condition that selects it: use close_browser to stop the browser. This gives clear when-to-use and when-not-to-use guidance for a simple tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources