Chrome Browser Control

by vKongv

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Name browser session

name_session

Assign a descriptive name to a browser control session to simplify status tracking and debugging.

Instructions

Set a human-readable browser-control session name for status, logs, and debugging.

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": {
      "name": "<name>"
    },
    "name": "name_session"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Sep 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the name is used for status, logs, and debugging, which gives some side-effect insight beyond the parameter value. However, it does not state whether the name is persisted, overwritten, or how it appears in fragmented contexts, leaving some behavioral uncertainty.

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 highly readable sentence that front-loads verb the object and purpose. No wasted words or filler, and maximum clarity per word.

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 very simple tool with a single parameter and no output schema, the description is adequate to let an agent know what the tool does and what the parameter means. It doesn't discuss response-derived behavior, but the absence of output schema and the trivial complexity make the description almost complete, only revealing no details about overwriting or querying the current session name.

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?

The schema provides no property descriptions (0% coverage), so the description must compensate. It does clarify that the 'name' is a human-readable identifier used for logs/status/debugging, and the parameter name 'name' aligns with this. Yet it does not explain any formatting constraints or examples in detail beyond the schema's min/max length.

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 uses a specific verb ('Set') and resource ('browser-control session name'), and states the purpose ('for status, logs, and debugging'). It clearly distinguishes from sibling tools like browser_status or navigate by identifying the action of naming a session, with no ambiguity that it is a setter rather than a getter or mutating action.

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

Usage Guidelines3/5

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

There is no explicit when/where comparison to sibling tools. The description implies use 'for status, logs, and debugging', which faintly guides context, but no exclusions are provided. An agent may infer to use this when a readable label is needed, but it does not force or avoid any alternative.

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