Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

open_url

Navigates a Chrome tab to a specified URL, optionally targeting a tab ID and waiting for page load to complete.

Instructions

Navigate a tab to a URL in Google Chrome

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

Input Schema

NameRequiredDescriptionDefault
urlYesURL to navigate to
tabIdNoTarget tab ID (optional, uses active tab)
waitForLoadNoWait for page load to complete (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.2/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 behavioral burden and does not meet it. It does not state what happens if the URL fails to load, whether navigation is cancellable, whether the call is blocking, or what it returns; only the schema's waitForLoad param hints at load behavior.

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?

A single short sentence with zero wasted wording, and the core action is front-loaded. It is efficient, though its brevity leaves gaps addressed in other dimensions rather than being filled here.

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

Completeness3/5

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

The tool is simple (3 fully documented parameters, no output schema), so the description is close to sufficient for correct invocation. However, it omits failure behavior and whether a tab must already exist, which an agent needs before calling a navigation tool without annotations.

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%, so each parameter is already documented in the schema. The description adds no syntax, format, or edge-case meaning beyond that, so the baseline of 3 applies.

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 gives a specific verb and resource ('Navigate a tab to a URL') and names the environment (Google Chrome), which implicitly separates it from siblings like new_tab or reload_tab. It stops short of explicitly contrasting with those alternatives, so it is clear but not fully differentiated.

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?

Usage is only implied by the verb: it is the tool for sending an existing tab to an address. There is no explicit guidance on when to prefer new_tab, reload_tab, go_back, or switch_to_tab, nor any stated precondition such as the tab already existing.

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