Skip to main content
Glama

browser_navigate

Read-onlyIdempotent

Navigate the SAME tab: action 'forward' (history forward), 'reload', or 'goto' (needs url; browser.open starts a new tab/session, this keeps the current one). Returns the final URL and title.

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": {
      "page_id": "<page_id>",
      "action": "<action>"
    },
    "name": "browser_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
actionYes
page_idYes
timeout_msNo
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds useful behavior the annotations cannot: the current tab is preserved and the call returns the final URL and title. It says nothing about timeout behavior, navigation failures, or how long-running loads are handled.

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?

One dense sentence with the key scoping claim and return values front-loaded; nearly every clause earns its place. The parenthetical is slightly overloaded with two separate ideas (url requirement and tab-vs-session contrast), but nothing is redundant.

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 5-parameter navigation tool with no output schema, the definition supplies the action vocabulary, the conditional url requirement, and the return shape (final URL and title). The remaining gaps — timeout_ms semantics and page_id's role in a multi-tab session — are the only notable omissions.

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 only 20% (just in_workspace), so the description carries real weight — and it does define the action values (forward, reload, goto) that the schema leaves as a bare string with no enum, plus the conditional requirement of `url` for goto. However, page_id and timeout_ms remain entirely unexplained in both schema and description, leaving a required parameter's meaning to inference.

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 (navigate) and resource scope (the SAME tab), then enumerates the supported actions: forward, reload, goto. It does not address the sibling browser_navigate_back or clarify whether 'back' is also valid here, so sibling differentiation is partial rather than complete.

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?

Explicitly contrasts with browser.open: 'browser.open starts a new tab/session, this keeps the current one' — a genuine when-to-use decision rule. It gives no exclusion for history-back navigation, which is the closest sibling and the most likely source of a wrong call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.