touch-browser

by nangman-infra

Overview Schema Source Related Servers Discussions Admin

Rust

Local

Store Session Secret

tb_secret_store

Stores a sensitive value in daemon memory, linking it to a specific target reference for use during a browser session.

Instructions

Store a sensitive value only in daemon memory for a specific target ref.

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>",
      "value": "<value>"
    },
    "name": "tb_secret_store"
  }
}

Input Schema

Name	Required	Description
`sessionId`	Yes	The browser session to use for this operation.
`targetRef`	Yes	The target reference that this stored secret is intended for.
`value`	Yes	The sensitive value to store only in session memory.

Output Schema

Name	Required	Description	Default
`sessionId`	Yes
`stored`	Yes
`targetRef`	Yes
`secretCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 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 that this stored secret is intended for."

addedInput schema / properties / value / description

Added value: +"The sensitive value to store only in session memory."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "secretCount": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "sessionId": {
+      "type": "string"
+    },
+    "stored": {
+      "type": "boolean"
+    },
+    "targetRef": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "sessionId",
+    "stored",
+    "targetRef",
+    "secretCount"
+  ],
+  "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?

With no annotations provided, the description carries the full burden. It mentions 'only in daemon memory' (non-persistent) but omits key traits like whether it overwrites existing values, scope (do different targetRefs share storage?), or security implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single 10-word sentence is concise and front-loaded. It communicates the core action without extra words, though it could be slightly expanded for clarity without losing efficiency.

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?

Given the existence of an output schema and the complexity of session management, the description lacks context about the lifecycle of the stored secret, how it interacts with sessions, and when it should be used. More detail on typical use cases would improve completeness.

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 each parameter has a description. The tool description adds little beyond the schema: it echoes 'target ref' but no new semantics. Baseline 3 is appropriate.

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 uses a specific verb ('Store') and resource ('sensitive value') and adds the detail 'only in daemon memory for a specific target ref.' This clearly distinguishes it from siblings like tb_secret_clear (clearing) and tb_type_secret (typing into an element). However, it could be more explicit about it being a session secret.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., tb_type_secret) or prerequisites. It simply states the action without context or exclusions.

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