Browser Session MCP

Overview Schema Source Related Servers Discussions Admin

get_stealth

Read-only

Check whether stealth mode is enabled for a browser session before running evaluations or reading console messages; returns the current setting without changing it.

Instructions

Return whether stealth is on for a session; it changes nothing. Check it before evaluate or list_console_messages, whose behavior it changes; use set_stealth to change it. A new session starts with stealth off.

Input Schema

Name	Required	Description	Default
`sessionId`	Yes	The id returned by open_browser_session. Errors if no open session has it.

Output Schema

Name	Required	Description	Default
`stealth`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.5Oct 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "properties": {
+    "stealth": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "stealth"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 23, 2026
- addedInput schema / properties / sessionId / description
```
Added value: +"The id returned by open_browser_session. Errors if no open session has it."
```
First observedv0.1.2Oct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds concrete behavioral context beyond them: it changes nothing, it affects the behavior of evaluate and list_console_messages, and a new session starts with stealth off. These are actionable traits not captured by the structured fields.

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?

Three short clauses, front-loaded with what the tool does and immediately followed by when to use it and the alternative. Every sentence carries distinct information.

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

Completeness5/5

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

Given the output schema and read-only annotation, the description supplies everything else an agent needs: the default state, the tools whose behavior it affects, and the mutating counterpart. No gaps remain for a one-parameter read tool.

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% and the sessionId parameter is fully documented, including the error behavior for missing sessions. The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb (returns whether stealth is on) and resource (for a session), and explicitly distinguishes it from set_stealth, which mutates the setting. An agent can identify its role without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance (check before evaluate or list_console_messages), names the mutating alternative (set_stealth), and states the default for a new session. No important routing decision is left to inference.

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