Skip to main content
Glama
Sign In
chromaphore-mcp

chromaphore-mcp

Official
by nodriver-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Open the browser

browser_open

Launch a headed or headless browser and return the profile path and fingerprint seed so later sessions can restore the same cookies, logins, storage, and fingerprint.

Instructions

Launches the browser. Answers with the profile path and the fingerprint seed in use: pass them back on a later browser_open to return to the same cookies, logins and storage (profile) and the same fingerprint (seed). Headless runs without a window; headed (the default) lets the user watch.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA page to open in the first tab.
seedNoFingerprint seed: the same seed gives the same fingerprint. Omit for a random one.
profileNo"new" (the default) for a fresh profile kept on disk; "temp" for a fresh one deleted when the browser closes, with its downloads and saved fetches; or the path of one a previous browser_open returned.
headlessNoRun without a window (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and mostly meets it: it discloses the return payload, the state-persistence contract, and the visible-vs-headless distinction. It leaves some behavior unstated, such as what happens on concurrent opens or whether launch blocks until the page loads.

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 sentences, front-loaded with the action and the return contract, with no redundant or filler wording. Every clause adds information an agent needs, and the headed/headless default is stated in a compact parenthetical.

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

Completeness4/5

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

There is no output schema, so the description correctly spends space describing the return values, and all four parameters are covered by the schema. The one gap is the surrounding lifecycle: no mention that browser_install may be required first or how this interacts with browser_close.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining the purpose of the returned profile path and seed as round-trip inputs for restoring session state, which the schema fields only hint at. It does not restate the url or headless parameters, but those are already fully documented.

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?

"Launches the browser" is a specific verb plus resource, and the follow-on sentence explains exactly what the call yields (profile path and fingerprint seed). That immediately separates it from siblings like browser_close, browser_install and fingerprint, which an agent can rule out without opening their schemas.

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

Usage Guidelines4/5

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

The description gives concrete usage guidance for the return values: pass the profile path and seed back on a later browser_open to resume cookies, logins, storage and fingerprint. It also states headed is the default and headless draws no window. It stops short of exclusion-style guidance, e.g. when not to open a new browser versus reusing an existing one, or whether browser_install must run first.

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