Skip to main content
Glama
Sign In
touch-browser

touch-browser

by nangman-infra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Select Active Tab

tb_tab_select

Switch the active tab of a browser session to a specified tab to direct subsequent actions to that tab.

Instructions

Set the active daemon tab for a session.

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>",
      "tabId": "<tabId>"
    },
    "name": "tb_tab_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesThe browser session to use for this operation.
tabIdYesThe specific tab to use inside the session. If omitted, the active tab is used.

Output Schema

NameRequiredDescriptionDefault
sessionIdYes
activeTabIdYes
tabYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.0
    • addedInput schema / properties / sessionId / description
      Added value: +"The browser session to use for this operation."
    • addedInput schema / properties / tabId / description
      Added value: +"The specific tab to use inside the session. If omitted, the active tab is used."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "activeTabId": {
+      "type": "string"
+    },
+    "sessionId": {
+      "type": "string"
+    },
+    "tab": {
+      "additionalProperties": false,
+      "properties": {
+        "active": {
+          "type": "boolean"
+        },
+        "currentUrl": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "hasState": {
+          "type": "boolean"
+        },
+        "latestSearchQuery": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "latestSearchResultCount": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "sessionFile": {
+          "type": "string"
+        },
+        "snapshotCount": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "tabId": {
+          "type": "string"
+        },
+        "visitedUrlCount": {
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "tabId",
+        "active",
+        "sessionFile",
+        "hasState",
+        "visitedUrlCount",
+        "snapshotCount",
+        "latestSearchResultCount"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "sessionId",
+    "activeTabId",
+    "tab"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states 'Set the active daemon tab' without mentioning side effects, error conditions, or what happens if the tab does not exist. This is insufficient for safe invocation.

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, compact sentence that efficiently communicates the core action. No wasted words, appropriate for a simple operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite high schema coverage and an output schema, the description lacks critical context such as behavioral implications of selecting a tab, error handling, or relationship to other tab operations. The tool is simple but the description is too sparse to be fully actionable.

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 existing parameter descriptions are adequate. The tool description adds no extra meaning beyond the schema, so it meets the baseline of 3.

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 clearly states the verb 'Set' and resource 'active daemon tab', distinguishing from sibling tools like tb_tab_close or tb_tab_list. However, 'daemon tab' is somewhat jargon, and the purpose is clear but not exceptionally detailed.

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 such as tb_tab_open or tb_tab_list. No prerequisites or exclusions mentioned, leaving the agent without context for appropriate usage.

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