touch-browser

by nangman-infra

Overview Schema Source Related Servers Discussions Admin

Rust

Local

Get Session Policy Profile

tb_profile

Retrieves the active policy profile for a specified browser session and tab.

Instructions

Return the active policy profile for a 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>"
    },
    "name": "tb_profile"
  }
}

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

B3.3/5.0

Behavior2/5

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

No annotations are provided, so description must carry full burden. It only says 'Return' implying read-only, but doesn't disclose side effects, permissions, or behavior on missing session/tab.

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, no redundancy, front-loaded with purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a tool with high schema coverage and output schema, but lacks explanation of what a policy profile is and how it relates to sessions; no mention of exclusions or prerequisites.

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 baseline is 3. Description adds no extra meaning beyond what the schema already provides for sessionId and tabId.

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 clearly states it returns the active policy profile for a daemon session/tab, using a specific verb and resource, and distinguishes from siblings like tb_profile_set and tb_policy.

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 like tb_policy or tb_profile_set; no when-to-use or when-not-to-use information.

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