Skip to main content
Glama

detach_browser

Disconnect the CDP bridge to end browser control while leaving your browser and tabs open. Restart the browser normally afterward to drop the debug port.

Instructions

Disconnect the CDP bridge. NEVER closes your browser or tabs. Restart the browser normally afterwards to drop the debug port.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the critical non-destructive guarantee ('NEVER closes your browser or tabs') and the post-condition that the user must restart the browser to drop the debug port. It does not cover failure behavior or whether the call is safe to repeat.

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, both front-loaded with the most decision-relevant information: the action first, then the reassurance that nothing is destroyed. The caps on NEVER emphasise the one fact most likely to be misread. Nothing is wasted.

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, no-annotation, no-output-schema tool, the description covers the action, the side-effect boundary, and the required cleanup step. It is nearly complete; only error or non-attached conditions are left unaddressed, which is minor at this complexity.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline of 4 applies. The schema is empty and fully consistent with the described behavior.

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 states a specific verb and resource: disconnect the CDP bridge, which plainly opposes the attach_browser sibling. It is clear what the tool does, though it never names attach_browser as its counterpart, so differentiation is by inference rather than explicit routing.

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 implied rather than stated: 'Restart the browser normally afterwards to drop the debug port' gives the follow-up step once the bridge is detached. There is no explicit when-to-use trigger such as 'call this when you are finished with the debug session' and no named alternative, so the agent must infer the timing.

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