Skip to main content
Glama

Close a browser session

browser_close
Idempotent

End a browser session to stop billing as soon as you are done; closing an already-ended session is safe.

Instructions

End a browser session and stop paying for it. Call it as soon as you are done with a session. Closing one that already ended is not an error.

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": {
      "session_id": "<session_id>"
    },
    "name": "browser_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesThe session_id `browser_open` returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.14.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and idempotentHint=true, so the safety bar is covered. The description adds real value beyond them by disclosing the cost model (billing stops on close), which is the primary reason an agent should call it promptly. The 'already ended is not an error' sentence largely restates idempotentHint, which keeps this from a 5.

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?

Three short sentences, zero filler, with the action and its motivation front-loaded before the edge-case reassurance. Nothing could be cut without losing information.

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 terminal tool with no output schema, this covers purpose, timing, cost consequence, and the idempotent edge case. An agent has everything needed to call it correctly and at the right moment.

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 single parameter is documented as 'The session_id browser_open returned,' so the description need not repeat it. It adds no format or provenance detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('End a browser session') and pairs it with the observable consequence ('stop paying for it'), which makes it unmistakable and clearly the counterpart to browser_open. No agent could confuse this with browser_click or browser_goto.

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

Usage Guidelines4/5

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

Gives explicit timing guidance: 'Call it as soon as you are done with a session.' It also pre-empts the one edge case an agent might hesitate over, i.e. a session that already ended. There is no named alternative, but for a terminal cleanup action none is really needed.

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