Skip to main content
Glama
Sign In
chromaphore-mcp

chromaphore-mcp

Official
by nodriver-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Install the browser

browser_install

Downloads, verifies and unpacks the Chromaphore browser release so the MCP server can drive a local browser. Call with check_only first to report installed and latest versions without downloading.

Instructions

Downloads the latest Chromaphore release from GitHub (about 1.6 GB with its fonts), checks its SHA-256 and unpacks it under %LOCALAPPDATA%\Chromaphore, replacing an older installed release; downloads nothing when the latest is already installed. With check_only it only reports what is installed and what the latest release is, and never downloads: call that first, and ask the user before a call that would download. Not needed when a browser path is set in the plugin settings.

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_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
check_onlyNoReport the installed release and the latest one on GitHub; download nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the ~1.6 GB download size, checksum verification, install location, replacement of an older release, and the no-op case when already current. It stops short of saying what a downloading call returns (path, version) or whether a partial/failed unpack leaves residue, which matters for a destructive-ish install.

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?

Two sentences, front-loaded with the action and its side effects, then the read-only mode and the consent prerequisite. Every clause (size, hash check, install path, replacement, skip-if-current) carries operational weight; nothing is filler.

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?

For a single-boolean install tool with no output schema and no annotations, the description covers cost, safety, idempotency, and preconditions. The only meaningful gap is the return value of a downloading call, which the agent would need to confirm success.

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 boolean is already documented; the description nevertheless adds real meaning — check_only 'never downloads', reports both installed and latest, and is recommended as the first call. That is behavioral semantics beyond the schema, above the baseline 3.

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 names a concrete verb and resource chain — download the latest Chromaphore release from GitHub, verify SHA-256, unpack under %LOCALAPPDATA%\Chromaphore — which no sibling tool does. It is immediately distinguishable from browser_open/navigate/observe, which assume a browser already exists.

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?

Explicit sequencing ('call that first'), an explicit exclusion ('Not needed when a browser path is set in the plugin settings'), and an explicit consent rule ('ask the user before a call that would download'). All three when/when-not/alternative signals are present.

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