Skip to main content
Glama
Sign In
Chrome Dialog MCP

Chrome Dialog MCP

by mikebeaton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

close_chrome

Closes only the Chrome session tied to browser_token and revokes its token, leaving other managed sessions open. Use when you need to end a specific browser session without stopping others.

Instructions

Explicitly close only the Chrome session identified by browser_token and revoke its token on success. Other managed sessions remain open. The reusable browser normally remains open across tasks; do not close it automatically at task completion. An absent broker returns not_connected, not proof that Chrome has exited.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "browser_token": "<browser_token>"
    },
    "name": "close_chrome"
  }
}

Input Schema

NameRequiredDescriptionDefault
browser_tokenYesPrivate capability token for this managed browser session; use the token returned by launch_chrome.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.5/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 well: it discloses the side effect (token revoked on success), the blast radius (other managed sessions unaffected), and an error-semantics caveat about not_connected. It stops short of describing the success return value or whether the underlying Chrome process is terminated versus just deregistered.

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?

Four short sentences, front-loaded with the action and scope before the caveats. Every sentence contributes, though the final broker/not_connected sentence is syntactically dense and could be split for clarity.

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 one-parameter, no-output-schema tool this covers intent, scope, side effects, and a failure-mode caveat. The only remaining gap is what a success response looks like, which is minor since no output schema is declared.

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% and the single parameter is already documented with an origin ('use the token returned by launch_chrome'). The description adds one useful semantic not in the schema: the token is revoked as a consequence of a successful close, reinforcing that this value is a capability that is consumed.

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 and resource: 'Explicitly close only the Chrome session identified by browser_token and revoke its token on success.' Scope is bounded ('only... Other managed sessions remain open'), which cleanly separates it from launch_chrome and the dialog siblings.

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?

Explicitly prescribes when to use (explicit close of one session) and when not to ('do not close it automatically at task completion'), and the phrase 'the reusable browser normally remains open across tasks' explains the rationale. It also warns that 'not_connected' from an absent broker is not evidence Chrome exited, preventing a common misdiagnosis.

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