touch-browser

by nangman-infra

Overview Schema Source Related Servers Discussions Admin

Rust

Local

Refresh Live Session

tb_refresh

Refresh the active headless research tab to reflect updated queries or filter changes.

Instructions

Refresh the current headless research tab after query or filter changes.

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

Input Schema

Name	Required	Description	Default
`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.

Output Schema

Name	Required	Description	Default
`sessionId`	Yes
`tabId`	Yes
`diagnostics`	No
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.7.0Jun 12, 2026

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": {
+    "diagnostics": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "result": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "sessionId": {
+      "type": "string"
+    },
+    "tabId": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "sessionId",
+    "tabId",
+    "result"
+  ],
+  "type": "object"
+}

First observedv0.1.11Apr 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, so description must carry full burden. Only states 'refresh' without detailing side effects, prerequisites, authentication needs, or what happens to the tab state. Insufficient for a mutation-like tool.

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, front-loaded with verb and resource, zero wasted words. Efficiently conveys core action.

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?

With no annotations and a simple description, the tool lacks behavioral context. Output schema exists but doesn't explain refresh behavior. For a tool with 2 parameters and sibling tools, more detail expected.

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% with descriptions for both parameters. Description adds no extra meaning beyond restating the schema context, so baseline 3 applies.

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?

Description clearly states verb 'Refresh' and resource 'current headless research tab' with context after query/filter changes. Distinguishes from sibling tab tools like tb_tab_open or tb_tab_select, but 'current' may conflict with tabId parameter.

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 explicit guidance on when to use this tool vs alternatives. Context 'after query or filter changes' is implied but not elaborated. No exclusions or when-not scenarios provided.

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