touch-browser

by nangman-infra

Overview Schema Source Related Servers Discussions Admin

Rust

Local

Click Interactive Target

tb_click

Click interactive targets inside an existing browser session or tab, with risk acknowledgment for supervised actions.

Instructions

Click an interactive target inside an existing daemon session/tab.

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>",
      "targetRef": "<targetRef>"
    },
    "name": "tb_click"
  }
}

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.
`targetRef`	Yes	The interactive element reference to click.
`ackRisks`	No	The supervised risk codes acknowledged for this action.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.7.0Jun 12, 2026

addedInput schema / properties / ackRisks / description

Added value: +"The supervised risk codes acknowledged for this action."

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."

addedInput schema / properties / targetRef / description

Added value: +"The interactive element reference to click."

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

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention side effects, required permissions, or what happens after the click (e.g., navigation, waiting). The ackRisks parameter implies risks but they are not explained.

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 a single sentence of 10 words, front-loaded with the core action. No extraneous information; every word is necessary.

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 having an output schema and 4 parameters with full schema coverage, the description is too minimal. It does not explain the concept of 'interactive target', how to obtain a targetRef, or the significance of ackRisks, leaving significant gaps for an agent.

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 all parameters have descriptions. The tool description adds no additional parameter meaning beyond what the schema provides, meeting the baseline of 3.

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 a specific verb ('Click') and resource ('interactive target') along with context ('inside an existing daemon session/tab'), clearly distinguishing it from sibling tools like tb_type or tb_submit.

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, nor any exclusion criteria or prerequisites. The description is purely declarative without usage context.

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