Skip to main content
Glama

Close a browser session

writ_browser_cancel
DestructiveIdempotent

Closes an open browser session (an open cloud browser bills until it is closed). Unsaved work that did more than visit pages is auto-saved first and the reply names it; discard=true keeps nothing.

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

Input Schema

NameRequiredDescriptionDefault
discardNoThrow away unsaved steps instead of auto-saving.
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / discard / description
      Previous value: -"true = the session's unsaved steps and functions are thrown away instead of auto-saved. Default false."New value: +"Throw away unsaved steps instead of auto-saving."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description goes further by disclosing the exact destruction semantics: what is auto-saved, that the reply names the saved work, and that discard=true keeps nothing. This is the precise behavioral detail an agent needs before a destructive close.

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 tightly packed sentences, front-loaded with the action, then the billing rationale, then the save/discard behavior. No filler.

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 2-parameter destructive mutation with no output schema, the description covers the key concerns: destruction behavior, auto-save, and the reply naming saved work. It omits error behavior for an invalid or already-closed session_id, a minor gap.

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 description coverage is 50% – 'discard' is documented in the schema, but 'session_id' has none. The description reinforces discard's effect ('discard=true keeps nothing'), adding a little meaning, but it says nothing about session_id format or validity, so it only partially compensates for the coverage gap.

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 gives a specific verb and resource ('Closes an open browser session') plus the operational consequence (the session bills until closed). It is unambiguous versus siblings like writ_browser_act or writ_browser_compose, though it never explicitly names an alternative to contrast with writ_browser_sessions.

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?

The billing note ('an open cloud browser bills until it is closed') gives a clear condition for when to invoke this tool – when the session is finished. There are no explicit exclusions or named alternatives, so it stops short of the when-not guidance that would earn a 5.

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.