Skip to main content
Glama

navigate_forward

Move the browser session forward to the next page in its history, so you can revisit a page after going back.

Instructions

Navigate forward to the next page in the browser session history.

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_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNoTimeout in ms (default: 15000ms).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about failure behavior when no forward history exists, whether it waits for the page to finish loading, or how it interacts with the existing session. For a navigation tool with zero annotation coverage this is a notable gap.

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?

A single, front-loaded sentence with no redundant wording. It is efficient, though its brevity is partly the cause of the missing behavioral detail rather than purely a virtue.

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?

This is a simple one-parameter tool with no output schema, so the description covers the core action, but it omits the one thing an agent most needs for a history-navigation tool: what happens when no forward entry exists. Adequate but with a clear gap.

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 description coverage is 100% and the sole timeout parameter is fully documented in the schema, so the baseline is 3. The description adds no additional meaning about how the timeout applies to this specific navigation.

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?

The description states a specific verb ('Navigate forward') and a specific target ('the next page in the browser session history'), which is unambiguous and clearly distinct from the navigate_back sibling. It lacks only an explicit mention of the sibling to reach 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 Guidelines3/5

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

Usage is only implied: the phrase 'next page in the browser session history' suggests it applies when forward history exists, but the description never says when to prefer this over navigate_back or open_page, nor what to do when there is no forward entry. No exclusions or alternatives are named.

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