Skip to main content
Glama
Sign In
touch-browser

touch-browser

by nangman-infra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Create Browser Session

tb_session_create

Creates a headless browser research session for accessing public documentation and reference workflows. Optionally accepts a correlation id; returns a new empty tab ready for navigation.

Instructions

Create a headless research session for public docs and reference workflows. The caller may provide sessionId as a correlation id; otherwise the daemon generates one. The returned active tab is empty until tb_open or tb_search_open_top opens a page.

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

Input Schema

NameRequiredDescriptionDefault
sessionIdNoOptional caller-provided session identifier for external correlation. Use 1-128 ASCII letters, digits, hyphen, underscore, or colon.
allowDomainsNoDomains this session is allowed to visit.

Output Schema

NameRequiredDescriptionDefault
sessionIdYes
activeTabIdYes
headlessYes
allowDomainsYes
tabCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.0
    • addedInput schema / properties / allowDomains / description
      Added value: +"Domains this session is allowed to visit."
    • addedInput schema / properties / sessionId
      Added value: +{
+  "description": "Optional caller-provided session identifier for external correlation. Use 1-128 ASCII letters, digits, hyphen, underscore, or colon.",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "activeTabId": {
+      "type": "string"
+    },
+    "allowDomains": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "headless": {
+      "type": "boolean"
+    },
+    "sessionId": {
+      "type": "string"
+    },
+    "tabCount": {
+      "minimum": 1,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "sessionId",
+    "activeTabId",
+    "headless",
+    "allowDomains",
+    "tabCount"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.11

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses headless nature, sessionId correlation, and empty active tab behavior, but does not address potential side effects, permissions, or failure modes. Adequate but not comprehensive.

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 sentences, front-loaded with purpose, no extraneous words. Every sentence provides essential information.

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?

Given the simple tool with 2 optional params and an output schema, the description covers key behavioral context (empty tab, correlation ID). Some additional context on error handling or session lifecycle would be beneficial, but the output schema likely handles return values.

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 100%, so baseline is 3. The description adds value for sessionId (noting daemon generation if omitted) but adds nothing for allowDomains, thus meeting but not exceeding the baseline.

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?

The description clearly states 'Create a headless research session for public docs and reference workflows', providing a specific verb and resource that distinguishes it from sibling tools like tb_session_close or 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 Guidelines3/5

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

The description implies usage for creating research sessions but lacks explicit guidance on when to use this tool over alternatives, such as when to create a new session vs reuse an existing one. No exclusions or prerequisites are mentioned.

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

Deploy Server

Other Tools