Skip to main content
Glama

Browser Navigate

browser_navigate

Navigates a browser session to a specified URL, with optional session targeting and agent binding. Use SAP login for credentialed SAP sign-in instead.

Instructions

Navigate to a URL. For SAP login, use sap_login instead - it handles credentials and session setup.

Session parameter:

  • session=None (default): Uses primary session ("s1")

  • session="s2": Targets specific session (for parallel agents)

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
urlYesURL to navigate to.
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.

Output Schema

NameRequiredDescriptionDefault
urlYesURL navigated to
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
titleNoPage title after navigation
successNoWhether the operation succeeded
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the session-routing model (default targets primary session "s1", named sessions for parallel agents). It says nothing about whether navigation blocks until load, what happens on timeout or bad URL, or how it interacts with the bound agent. Those are the behaviors an agent most needs for a browser navigation call.

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 short blocks: the core action plus sibling routing first, then a bulleted session explanation. Every sentence carries information an agent needs, and the most important constraint is front-loaded.

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?

An output schema exists and the input schema is fully documented, so return values and parameter shapes need not be restated. However, for a navigation tool with no annotations, the description leaves out error/timeout behavior and the purpose of agent_id, leaving meaningful gaps for an agent deciding how to call it safely.

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 100%, so the baseline is 3. The description does add meaning to session by explaining that the default resolves to primary session "s1" and that explicit sessions exist for parallel agents, but agent_id — the binding-check parameter — is never mentioned in the description at all.

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 ("Navigate to a URL") and explicitly separates itself from sap_login for the SAP login case. It does not distinguish itself from the other browser_* siblings, but the primary ambiguity an agent would hit is resolved.

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?

Gives an explicit when-not: for SAP login use sap_login instead, with the reason (credential and session setup). It also frames the session parameter around the parallel-agent scenario. No guidance is given on when to prefer browser_wait or browser_snapshot after navigating, so it stops short of a full routing rule.

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