Skip to main content
Glama

navigate

Opens a URL in a shared browser tab or steps back, forward, or reloads the page, letting an agent control navigation in the tab you share with it.

Instructions

Go to a URL in a shared tab, or go back, forward or reload.

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
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
urlNo
actionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not disclose whether navigation waits for page load, what happens to unsaved page state, whether the call fails when the tab is not shared, or how url and action interact — all material for a state-changing browser operation.

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?

A single front-loaded sentence that enumerates the modes without filler. Nothing could be removed without losing information.

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

Completeness2/5

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

With no annotations, no output schema, and three parameters of which two are undescribed in the schema, the description is too thin. The zero-required-parameter design means the agent has no way to know the default or minimum viable invocation, which is a significant gap for a mutation-style tool.

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 33%: only 'tab' is documented there (with an example handle and optionality note). The description compensates partially by mapping the undocumented 'action' enum values to concrete behaviors and indicating 'url' is the destination. It does not clarify the precedence or exclusivity of url vs action, nor what happens when neither is supplied despite zero required parameters.

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 ('Go to') and resource ('a URL') and enumerates the alternative modes (back, forward, reload), so the agent knows exactly what operation this performs. It stops short of differentiating itself from siblings like open_tab, leaving the agent to infer that this navigates an existing tab rather than creating one.

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 phrase 'in a shared tab' implies a prerequisite (a tab must already exist and be shared), which is a useful implicit constraint. However, there is no explicit when-to-use guidance and no statement of when to reach for open_tab instead, so routing between the two is left to inference.

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