Skip to main content
Glama

browser_navigate

Read-only

Opens an allowlisted HTTPS URL in a persistent headless browser so clients can inspect approved web pages through permission-gated automation.

Instructions

Open allowlisted HTTPS URL in persistent headless browser

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

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false; the description adds two useful behavioral facts: the browser is persistent/headless and only allowlisted HTTPS URLs are permitted. It does not describe return behavior, wait/load semantics, or what happens to the prior page, so it adds moderate but not rich context.

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 front-loaded sentence with no filler; every phrase (open, allowlisted HTTPS, persistent headless) carries selection or constraint information.

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 one-parameter navigation tool with annotations covering safety and side effects, the description supplies the essential invocation constraint and execution context. It leaves return/load semantics unstated, but no output schema exists and the complexity is low, so the definition is largely complete enough to invoke correctly.

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 coverage is 0% and the single url parameter is only typed as string in the schema; the description compensates somewhat by stating the URL must be an allowlisted HTTPS URL. It does not give format examples, allowlist mechanics, or other syntax, so the added meaning is meaningful but incomplete.

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 ('Open') and resource ('allowlisted HTTPS URL') with execution context ('persistent headless browser'), so an agent can distinguish it from interaction tools like browser_click. It does not explicitly name a sibling alternative, so it falls short of a 5.

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?

The description implies the tool is used to open allowlisted HTTPS URLs, which gives some selection context, but it never states when to choose it over sibling browser_* tools or when navigation is inappropriate. No explicit when/when-not guidance is present.

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