Skip to main content
Glama

web_forward

Moves a specified or active tab forward one history entry, like a browser Forward button, to revisit the next page.

Instructions

Go forward one entry in the tab's history (like the browser's Forward button).

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

Input Schema

NameRequiredDescriptionDefault
target_idNoTab id from web_tabs. Omit to use the first/active tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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. The browser-Forward analogy does convey real behavior (moves the session-history pointer, presumably a no-op when no forward entry exists), but it says nothing about whether the call waits for the page to load, what happens on failure, or whether it requires the tab to be active.

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, with zero filler; the parenthetical analogy earns its place by anchoring behavior. It could be a touch tighter but nothing is wasted.

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?

Adequate for a one-optional-param tool with a fully described schema and no output schema, but it leaves open the end-of-history edge case and load-timing behavior, which matter for an agent sequencing navigation calls.

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% and the single optional target_id is fully documented, including the sensible 'omit to use first/active tab' default. The description adds nothing beyond the schema, so baseline 3 applies.

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?

Specific verb ('Go forward') plus resource ('one entry in the tab's history') with a concrete browser-Forward analogy, which makes it unmistakably the inverse of web_back. It doesn't name a sibling explicitly, but the purpose is unambiguous.

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: an agent infers you call this when the target tab has a forward history. There is no statement of when not to use it (e.g. no forward history available) or how it relates to web_navigate/web_back.

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