Skip to main content
Glama
Sign In
Browser MCP

Browser MCP

by drisplabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Go Forward

go_forward

Navigate forward in browser history and receive a refreshed page snapshot with interactive elements highlighted.

Instructions

Go forward one page in browser history. Returns a fresh page snapshot of the resulting page with its interactive elements.

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

Input Schema

NameRequiredDescriptionDefault
page_idNoPage ID. If omitted, operates on the most recently used page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / page_id / description
      Added value: +"Page ID. If omitted, operates on the most recently used page."
  2. First observedv4.6.4

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It states it returns a fresh snapshot but discloses no other behavioral details such as whether the tool waits for page load, what happens if no forward history, or any side effects like losing current state. Insufficient for an AI agent to predict behavior.

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 sentences, no wasted words. Front-loaded with action and return value. Efficient and clear.

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

Completeness4/5

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

For a simple tool with no output schema, the description explains the return value adequately. However, it omits edge-case behavior (e.g., when no forward history) and does not mention if the snapshot is synchronous or not. Still mostly complete given the tool's simplicity.

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% (one parameter 'page_id' with description). The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 verb 'go forward' and resource 'one page in browser history', and explicitly mentions the return value: a fresh page snapshot with interactive elements. This distinguishes it from the sibling tool 'go_back'.

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?

Implied usage is for forward navigation in browser history, but no explicit guidance on when to use versus alternatives (e.g., 'navigate') or when not to use (e.g., if no forward history). The sibling list includes 'go_back' which provides context but no direct instructions.

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

Deploy Server

Other Tools