touch-browser

by nangman-infra

Overview Schema Source Related Servers Discussions Admin

Rust

Local

Close Session

tb_session_close

Closes a specified browser daemon session and removes all associated tab data to free resources.

Instructions

Close a daemon session and clean up all tab state.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "tb_session_close"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes	The browser session to use for this operation.

Output Schema

Name	Required	Description	Default
`sessionId`	Yes
`removed`	Yes
`removedTabs`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.7.0Jun 12, 2026

addedInput schema / properties / sessionId / description

Added value: +"The browser session to use for this operation."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "removed": {
+      "type": "boolean"
+    },
+    "removedTabs": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "sessionId": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "sessionId",
+    "removed",
+    "removedTabs"
+  ],
+  "type": "object"
+}

First observedv0.1.11Apr 15, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Discloses destructive behavior (closing session, cleaning tab state) but no details on side effects or reversibility. No annotations provided to supplement.

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?

Single sentence with no fluff. Front-loaded with action and object. Efficient.

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?

Simple tool with output schema present but not described. No return value info. Adequate for basic use but could be more complete.

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 covers sessionId with generic description. Text adds no extra meaning beyond schema. Baseline score for 100% coverage.

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?

Description clearly states the tool closes a daemon session and cleans up tab state. Distinguishes from siblings like tb_session_create and tb_session_synthesize.

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 use this tool versus alternatives like tb_session_create or tb_status. Lacks when-not-to-use or prerequisites.

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