touch-browser

by nangman-infra

Overview Schema Source Related Servers Discussions Admin

Rust

Local

Clear Session Secret

tb_secret_clear

Delete a specific stored secret or all secrets from a browser session to protect sensitive data.

Instructions

Clear one stored daemon secret or all secrets 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>"
    },
    "name": "tb_secret_clear"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes	The browser session to use for this operation.
`targetRef`	No	The target reference whose stored secret should be cleared. Omit to clear all stored secrets for the session.

Output Schema

Name	Required	Description	Default
`sessionId`	Yes
`removed`	Yes
`secretCount`	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 / targetRef / description

Added value: +"The target reference whose stored secret should be cleared. Omit to clear all stored secrets for the session."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "removed": {
+      "type": "boolean"
+    },
+    "secretCount": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "sessionId": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "sessionId",
+    "removed",
+    "secretCount"
+  ],
+  "type": "object"
+}

First observedv0.1.11Apr 15, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The description identifies the tool as destructive (clearing secrets) but, with no annotations available, it omits details like required permissions or reversibility.

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 conveys the full purpose efficiently without fluff.

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?

With output schema present, return values need no explanation. The description covers core functionality adequately for a simple clear operation.

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 only paraphrases the schema (e.g., 'Omit to clear all stored secrets') without adding extra semantic value.

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 specific verb 'clear' and resource 'stored daemon secret or all secrets for a session', clearly distinguishing from sibling tools like tb_secret_store and tb_type_secret.

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 (to clear stored secrets) but provides no explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among sibling tools.

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