Skip to main content
Glama

navigate

Loads a URL in a browser tab, or moves back or forward in its history, then waits for page load and returns URL, tab ID, and status.

Instructions

Loads a URL in the tab, or moves back or forward in its history, and waits for load (at most 30 s; a breakpoint or dialog while loading fails at once saying so). Returns {url (after redirects), tab_id, browser, status?, notes?}. A network error, a download or a page behind HTTP authentication (log in with http://user:password@host/path) fails with 'Navigation failed: ()'. With --local only local addresses are allowed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoAbsolute URL (http, https or file); omit it to use 'history'.
tab_idNoDefault: the active tab.
historyNo'back' or 'forward' in the tab's history, instead of a 'url'.
instance_idNoDefault: 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A4.1/5.0
Behavior5/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 so: it discloses the 30 s wait, that a breakpoint or dialog fails immediately, the exact return object including redirect resolution, the failure string format, that downloads and HTTP-auth pages fail, and the --local address restriction.

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?

Front-loads the primary action and packs a lot of operational detail into three sentences without padding. The heavy parenthetical nesting makes it dense to parse, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description spells out the returned fields and the error shape, and it covers timeouts, auth and download edge cases. An agent has everything needed to call it and interpret both success and failure.

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 schema already documents url, tab_id, history enum and instance_id, setting the baseline at 3. The description only adds the hint that the returned url reflects post-redirect state and references a --local flag that is not actually a parameter.

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 ('Loads a URL in the tab') plus the secondary history back/forward mode, so the agent knows exactly what the tool does. It never distinguishes itself from the nearby 'reload' sibling, which is the main ambiguity risk, so it stops 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 Guidelines4/5

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

Gives concrete conditions: omit the url to use history, expect a hard 30 s load ceiling, and use embedded credentials (http://user:password@host/path) when a page sits behind HTTP authentication. It offers no explicit when-not guidance and never routes the agent to reload or open_tab instead.

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