Skip to main content
Glama
sessfork-browser
by wasabihu

browser_close

Destructive

Closes the headless browser and all open tabs to end a browsing session and release associated resources.

Instructions

Close the browser and all open tabs.

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 observedv0.1.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description additionally discloses the blast radius by stating that all open tabs are closed too. It does not say whether cookies, local storage or unsaved form data survive, or whether a later browser_navigate will relaunch the browser, which would be the remaining valuable disclosures.

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 zero filler, sized correctly for a no-argument teardown tool.

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 simple zero-parameter destructive action with annotation coverage but no output schema, the description covers what the tool does and what it destroys. Only the post-close state semantics (session persistence, possibility of relaunch) are left unstated.

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 semantics to explain and the baseline applies. The description correctly avoids inventing arguments the schema would reject.

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?

A specific verb plus resource ('Close the browser') makes the action unambiguous, and the added scope ('and all open tabs') tells the agent this is terminal, not per-tab. It does not explicitly contrast with tab-level siblings like browser_tabs, but the intent is clear from the name and text alone.

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 when-to-use or when-not-to-use guidance is given; the agent must infer that this is a session-teardown action. There is no mention of alternatives such as closing a single tab, nor any note on whether the browser can be relaunched afterwards.

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