touch-browser

by nangman-infra

Overview Schema Source Related Servers Discussions Admin

Rust

Local

Open Top Search Results

tb_search_open_top

Open the top search results into new tabs to initiate evidence-grounded research across multiple pages.

Instructions

Open the top recommended search results into new research tabs. Prefer this immediately after tb_search, then inspect tabs with tb_read_view before tb_extract.

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_search_open_top"
  }
}

Input Schema

Name	Required	Description
`sessionId`	Yes	The browser session to use for this operation.
`tabId`	No	The specific tab to use inside the session. If omitted, the active tab is used.
`limit`	No	The maximum number of top-ranked search results to open.

Output Schema

Name	Required	Description	Default
`sessionId`	Yes
`searchTabId`	Yes
`openedCount`	Yes
`openedTabs`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.7.0Jun 12, 2026

addedInput schema / properties / limit / description

Added value: +"The maximum number of top-ranked search results to open."

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": {
+    "openedCount": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "openedTabs": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "diagnostics": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "result": {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          "selectedResult": {
+            "additionalProperties": false,
+            "properties": {
+              "domain": {
+                "type": "string"
+              },
+              "officialLikely": {
+                "type": "boolean"
+              },
+              "rank": {
+                "minimum": 1,
+                "type": "integer"
+              },
+              "recommendedSurface": {
+                "type": "string"
+              },
+              "selectionScore": {
+                "type": "number"
+              },
+              "snippet": {
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              },
+              "url": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "rank",
+              "url",
+              "title",
+              "snippet",
+              "domain",
+              "officialLikely",
+              "recommendedSurface",
+              "selectionScore"
+            ],
+            "type": "object"
+          },
+          "tabId": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "tabId",
+          "selectedResult",
+          "result"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "searchTabId": {
+      "type": "string"
+    },
+    "sessionId": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "sessionId",
+    "searchTabId",
+    "openedCount",
+    "openedTabs"
+  ],
+  "type": "object"
+}

First observedv0.1.11Apr 15, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the tool opens new tabs, but lacks details on side effects (e.g., whether it modifies existing tabs, required permissions beyond sessionId, or rate limits). The workflow hint adds minimal behavioral context but is 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?

The description is only two sentences: the first states the core action, the second provides usage guidance. No extraneous information. Every sentence adds value.

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 tool has an output schema (not shown but noted in context), the description does not need to explain return values. It adequately covers the action and workflow. However, it could be more explicit about relying on prior tb_search results, though this is implied.

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%, so baseline is 3. The description does not add any additional meaning to the parameters beyond the schema definitions. For example, it doesn't explain what 'top recommended' means or how the 'limit' parameter affects behavior.

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 uses the specific verb 'Open' and resource 'top recommended search results into new research tabs', clearly distinguishing it from sibling tools like tb_search (which performs search) and tb_search_open_result (which might open a specific result). The purpose is unambiguous.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool: 'Prefer this immediately after tb_search', and what to do next: 'inspect tabs with tb_read_view before tb_extract'. This provides clear workflow context and helps the agent decide correct sequencing.

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