Skip to main content
Glama

Close tab

browser_close

Closes the controlled Chrome tab and detaches from the browser session, ending automation control.

Instructions

Close the controlled Chrome tab and detach.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses very little. It implies a destructive/terminal operation but never states whether the tab can be recovered, whether unsaved page state is lost, whether the browser process also exits, or what happens to in-flight operations. "Detach" is the only hint of session teardown and it is left undefined.

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?

A single front-loaded sentence with no filler. Every clause ("close the controlled Chrome tab" and "detach") conveys distinct information, even if "detach" would benefit from elaboration.

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 zero-parameter, zero-annotation tool the description is nearly sufficient to invoke it, but not to predict its consequences. An agent cannot tell from this definition whether closing is reversible, whether it frees the controlled browser for reuse, or which errors might result.

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 nothing for the description to disambiguate; the baseline of 4 applies. The empty object schema is consistent with the description, which describes a parameterless action.

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 and resource ("Close the controlled Chrome tab") and adds a second effect ("detach"), which distinguishes it from navigation siblings like browser_back or browser_navigate. The only weakness is that "detach" is not defined, so the agent must guess whether the session, browser process, or both are torn down.

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 on when to call this versus leaving the tab open, and no preconditions or follow-up steps are given. Nothing tells the agent that subsequent browser_* calls will fail after closing, or that a new navigation session is required.

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