Skip to main content
Glama

browser_open

Read-onlyIdempotent

Opens an approved HTTP(S) site in a dedicated Chrome profile; unapproved URLs return local PowerShell approval steps instead. Never auto-approves sites.

Instructions

Open an approved HTTP(S) site in the dedicated Chrome profile; otherwise return local PowerShell approval instructions. Never self-approves websites.

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

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, idempotent and closed-world; the description adds real value beyond that by disclosing the approval gate, the dedicated-profile isolation, and that failure returns local PowerShell approval instructions rather than proceeding. 'Never self-approves websites' is a meaningful guardrail the annotations do not convey. It stops short of saying whether the call blocks or what a successful return looks like.

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 compact clauses with the primary action front-loaded and the fallback second; no filler, and the approval guardrail lands last as a memorable constraint.

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-URL navigation tool with rich annotations and no output schema, the description covers the main branch, the failure branch, and the security constraint. The remaining gap is the undefined notion of 'approved' and whether prior session state is required.

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?

With one parameter at 0% schema description coverage, the description must carry the load. It adds the key constraint that the URL must be 'approved' and HTTP(S)-only, which goes beyond the schema's bare format:uri, but it never explains how approval status is determined or what happens for other schemes.

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?

States a specific verb and resource ('Open an approved HTTP(S) site in the dedicated Chrome profile') plus the fallback outcome. It is clearly distinct from siblings like browser_click or browser_screenshot, though it never explicitly names the navigation role relative to them.

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 implied: call it to navigate to an approved site, and expect approval instructions otherwise. There is no explicit when-not guidance, no mention of prerequisites (e.g., whether a browser session must already be running) and no pointer to alternatives for non-approved URLs.

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