OpenChrome

tabs_context

Read-onlyIdempotent

Retrieve session tab IDs grouped by worker to manage automation contexts. Filter by worker, scope, or request summary counts.

Instructions

Get session tab IDs grouped by worker.

Input Schema

TableJSON Schema

Name	Required	Description
`scope`	No	browser discovers unowned user tabs without adopting them; requires server opt-in.
`summary`	No	Return counts only, no tab details
`workerId`	No	Filter to a specific worker

Output Schema

TableJSON Schema

Name	Required	Description	Default
`workers`	Yes
`tabCount`	Yes
`sessionId`	Yes
`workerCount`	Yes
`defaultWorkerId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.15.0Sep 25, 2026

addedInput schema / properties / scope

Added value: +{
+  "description": "browser discovers unowned user tabs without adopting them; requires server opt-in.",
+  "enum": [
+    "session",
+    "browser"
+  ],
+  "type": "string"
+}

First observedv1.12.8Jun 18, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations (readOnlyHint, idempotentHint, destructiveHint=false) already cover the safety profile, and the description is consistent with them. It adds a small behavioral detail about grouping, but it does not explain the session-vs-browser scope behavior or any side effects such as adoption semantics, which remain in the schema.

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 seven-word sentence with no filler, front-loading the verb and resource before the grouping detail. Every word contributes to meaning.

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?

With a complete input schema, an output schema, and read-only/idempotent annotations, the description does not need to explain returns or safety. However, it omits material context about when the 'session' versus 'browser' scope should be used, which is important for correct invocation.

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%, with descriptions for scope, summary, and workerId, so the schema already documents the parameters fully. The description only hints at workerId through 'grouped by worker' and adds no additional parameter semantics beyond the schema.

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 states a specific verb ('Get'), a clear resource ('session tab IDs'), and the grouping dimension ('by worker'), which makes the tool's role obvious and distinguishes it from the mutation siblings tabs_create/tabs_close/tabs_activate. It does not explicitly name those alternatives, so it stops short of full sibling differentiation.

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 gives no guidance about when to use this tool versus tabs_create/tabs_close/tabs_activate or any other read tool. It neither states conditions for use nor mentions alternatives, leaving the agent to infer invocation context from the name alone.

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

Deploy Server