Skip to main content
Glama

open

Loads a webpage in a headless browser, waits for completion, solves Cloudflare challenges when enabled, and returns the final URL, title, and challenge status. Use it before other browser tools.

Instructions

Load a page in the browser and wait until it has loaded. Returns the final url and title. A Cloudflare challenge on the way is solved first (unless the server runs with --no-auto-solve); challenge then reports kind, solved and remaining ("none" once through). Call this before the other tools.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute address to load, e.g. `https://example.com/`.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.47-alpha
    • addedInput schema / properties / url / description
      Added value: +"Absolute address to load, e.g. `https://example.com/`."
  2. First observedv0.1.46

TDQS

A4.2/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 carries it well: it discloses that the call blocks until load, that a Cloudflare challenge is auto-solved unless the server runs `--no-auto-solve`, and that `challenge` reports `kind`/`solved`/`remaining` with `"none"` on success. It does not say whether navigation happens in the existing tab, what happens on timeout/DNS failure, or whether the previous page is lost — relevant for a stateful mutation of the browser session.

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?

Three dense sentences: what it does, what it returns, the caveat, then the call-order rule. Front-loaded and free of filler, with the challenge behavior parenthetically scoped rather than bloating the main clause.

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?

An output schema exists, so restating `url`/`title` is redundant but harmless, and the challenge-field detail is genuinely useful context. It is nearly complete for a one-parameter navigation tool; the remaining gap is failure/timeout behavior and tab semantics, which an agent needs to decide whether to retry or reset.

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 single `url` parameter is fully described in the schema (100% coverage), including an example, so the description doesn't need to compensate. The description adds no constraint beyond the schema (e.g., whether relative URLs or non-http schemes are rejected), so baseline 3 applies.

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?

"Load a page in the browser and wait until it has loaded" names a concrete action and the resource, and it is clearly distinguished from the sibling tools (snapshot, click, evaluate), which all operate on an already-open page. Return values are stated up front (final `url` and `title`).

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

Usage Guidelines4/5

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

"Call this before the other tools" gives an explicit ordering rule that selects this tool over all siblings. What's missing is the inverse: no guidance on when an agent might prefer `challenge_state`/`solve_challenge` directly (i.e., whether those are needed at all given the auto-solve).

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