Skip to main content
Glama

navigate

Load a URL in a browser tab and wait for the page to finish loading. Use back or forward to move through navigation history.

Instructions

Load a URL in a tab and wait for it. Use "back" or "forward" for history.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
tabIdNoAgent tab id from tabs_list. Omit to use the last agent tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.4

TDQS

B3.3/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 behavioral burden. It does disclose one meaningful trait — the call blocks until the page load completes ("wait for it") — but says nothing about failure modes, timeouts, what happens to the current page content, or whether navigation requires an existing tab.

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 sentences, front-loaded with the primary action and followed immediately by the exclusion rule. No filler or redundant restatement of the name.

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?

For a two-parameter navigation tool with no annotations and no output schema, the definition covers the core action but leaves the agent guessing about blocking behavior scope, failure handling, and the relationship to tab_open/tabs_list. It is minimally adequate rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: tabId is documented in the schema, while url has no format/semantics description in either place. The description says only "in a tab," which does not clarify that tabId refers to an agent tab or how the default (last agent tab) behaves — that meaning lives solely in the schema.

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?

"Load a URL in a tab and wait for it" gives a specific verb (load) and resource (URL, tab), and the second sentence distinguishes the operation from history traversal. It does not name any actual sibling tool (tab_open, click, page_text), so the differentiation against siblings in the catalog is only implicit.

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 excludes history traversal ("Use 'back' or 'forward' for history"), which is a useful when-not hint, but it gives no guidance on choosing between this and tab_open for opening a page, nor on when the tabId parameter should be supplied versus omitted.

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