Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

go_forward

Navigate forward in browser history to return to the next page for a tab, restoring forward navigation after going back.

Instructions

Navigate forward in browser 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": "go_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/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 burden. It does not say what happens when there is no forward history (error vs. silent no-op), whether the call waits for the navigation to complete, whether it invalidates cached snapshots, or what is returned.

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?

One sentence, front-loaded with the action and resource, with no filler. Its brevity is efficient, though it leaves no room for the behavioral caveats noted above.

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 simple one-optional-parameter navigation tool with no output schema, the description covers the core action adequately. It is incomplete on the edge cases that matter for browser-history tools: absent forward history and navigation-wait semantics.

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 single optional tabId parameter is documented in the schema as 'Tab ID (optional)'. The description adds nothing about it, but the baseline of 3 applies when the schema already does the documenting.

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 gives a specific verb and resource: 'Navigate forward in browser history,' which an agent can map directly to the counterpart of go_back. It stops short of naming go_back explicitly, so sibling differentiation is inferred from the direction word rather than stated.

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?

There is no when-to-use guidance, no statement of prerequisites (e.g., that forward history must exist), and no mention of go_back or reload_tab as alternatives. The agent must infer usage from the one-line purpose statement alone.

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