Skip to main content
Glama

browser_navigate_forward

Advance in the browsing history to return to a previously visited page, retrieving a fresh AI snapshot for current context.

Instructions

Go forward in history. Returns a fresh AI snapshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idNo
Behavior3/5

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

The description mentions that the tool 'Returns a fresh AI snapshot', which adds insight beyond the name. However, with no annotations present, it fails to disclose critical behaviors such as whether it requires an active session, what happens if no forward history exists, or side effects on the browser state.

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?

The description is extremely concise (one short sentence), which is generally good. It front-loads the action. However, it omits necessary details, but for conciseness, it is not wasteful—just incomplete.

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?

Given the tool's simplicity and the presence of many sibling browser tools, the description lacks completeness. It does not explain the required precondition (previous back navigation), session handling, or the relationship with other navigation tools, making it insufficient for correct autonomous use.

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

Parameters1/5

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

The input schema has one parameter (session_id) with no description, and the tool description does not explain its purpose, format, or default behavior. With 0% schema coverage, the description should compensate but does not add any meaning beyond the parameter name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Go forward') and the resource ('history'), making the tool's function immediately obvious. It distinguishes from sibling tools like 'browser_navigate_back' and 'browser_navigate' by specifying forward history movement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'browser_navigate_back' or 'browser_navigate'. There is no mention of prerequisites (e.g., needing a history entry ahead) or contextual use cases, leaving the agent to infer usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dawgswarm/dawg-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server