Skip to main content
Glama
Sign In
Browser[X]MCP

Browser[X]MCP

by rnd-pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

start_browser

Launch a browser instance for testing, with headless mode for streamlined automation in CI environments.

Instructions

Start browser instance for testing

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": "start_browser"
  }
}

Input Schema

NameRequiredDescriptionDefault
headlessNoRun browser in headless mode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-beta.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Start browser instance' without revealing side effects (e.g., opening a new window, network access), whether it blocks, or what happens if called repeatedly. This is minimal and insufficient for an agent to anticipate consequences.

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 a single concise sentence with no wasted words. It is appropriately brief for a simple tool, though it could incorporate some usage hints without becoming verbose.

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?

Given the tool's role as a likely entry point for browser automation, the description lacks essential context: no mention of when to invoke it, what it sets up for subsequent tools, or any prerequisites. It is incomplete for an agent trying to decide when and how to use it, even with a simple schema.

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%: the only parameter 'headless' is fully described in the schema. The description adds no parameter-specific information, but the baseline of 3 is appropriate since the schema already documents the parameter.

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

Purpose4/5

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

The description clearly states the verb 'Start' and resource 'browser instance', indicating the tool initializes a browser session. It implicitly distinguishes from sibling tools that perform navigation, input, or extraction, but the purpose is somewhat generic ('for testing') and could be more specific about the initialization role.

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?

No guidance is provided on when to use this tool versus alternatives, nor any mention of prerequisites or typical sequencing (e.g., call before navigate_browser). The description simply states what it does without context on appropriate usage.

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