Skip to main content
Glama
shaun0927

OpenChrome

by shaun0927
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

worker

Create isolated browser contexts for parallel automation, list active ones, or delete them to close tabs and free resources.

Instructions

Manage workers. Actions: "create" (isolated context), "list" (show all), "delete" (remove and close tabs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo(create) Custom ID. Auto-generated if omitted
nameNo(create) Worker name
tabIdNo(borrow_tab/release_tab) Explicit existing tab ID.
actionYesAction: create, list, or delete
workerIdNo(delete) Worker ID to delete
expectedUrlNo(borrow_tab) Exact URL observed by tabs_context scope=browser. Requires server opt-in; never closes the user tab on cleanup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.0
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "create",
-  "list",
-  "delete"
-]New value: +[
+  "create",
+  "list",
+  "delete",
+  "borrow_tab",
+  "release_tab"
+]
    • addedInput schema / properties / expectedUrl
      Added value: +{
+  "description": "(borrow_tab) Exact URL observed by tabs_context scope=browser. Requires server opt-in; never closes the user tab on cleanup.",
+  "type": "string"
+}
    • addedInput schema / properties / tabId
      Added value: +{
+  "description": "(borrow_tab/release_tab) Explicit existing tab ID.",
+  "type": "string"
+}
  2. First observedv1.12.8

TDQS

C2.4/5.0
Behavior1/5

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

The description explicitly says delete 'removes and closes tabs,' a destructive effect, while the annotations declare destructiveHint=false. This is a direct annotation contradiction. The description does add useful context like 'isolated context' for create, but the contradiction is severe.

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?

The description is compact, front-loaded with 'Manage workers,' and contains zero filler. It is efficiently organized as an action list with short parenthetical clarifications, though the brevity causes it to miss two enum actions.

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?

With six parameters, five enum actions, no output schema, and all annotations false, the description carries a heavy burden. It covers only three of five actions and gives no information about borrow_tab/release_tab semantics, worker ID usage, or cleanup behavior. This is materially incomplete 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 description coverage is 100%, so the baseline of 3 applies even though the description adds no parameter detail. The description actually omits the tabId and expectedUrl parameters relevant to borrow_tab/release_tab, but the schema individually documents all parameters. No additional meaning is provided beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('Manage workers') and gives parenthetical semantics for create, list, and delete. However, it omits the 'borrow_tab' and 'release_tab' actions that exist in the schema enum, making the stated purpose incomplete. It also does not distinguish this tool from sibling worker_update and worker_complete tools.

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 per-action semantics but no guidance on when this tool should be used versus worker_update, worker_complete, or other worker-related siblings. It mentions no prerequisites, conditions, or exclusions, leaving usage entirely to inference from the action names.

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

Deploy Server

Other Tools