Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

go_back_or_forward

Navigate a browser environment's history by moving back or forward, using the environment ID and an optional direction flag to control page navigation.

Instructions

Navigate browser history (back/forward) in the browser environment

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "envId": "<envId>"
    },
    "name": "go_back_or_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
envIdYesEnvironment ID for the browser environment to operate.
isForwardNoGo forward in history if true, go back if false (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden and does not fulfill it. It does not say whether traversal waits for page load, what happens when there is no history to go back or forward to, or whether it affects session state; it only restates the direction.

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 wasted words. It is efficient, although it could have used its brevity to add one useful clause, such as what happens when history is empty.

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?

The task is simple: two parameters, one required, with full schema coverage and no output schema. Even so, an agent still lacks behavioral details such as load-waiting, failure modes, and the distinction from 'navigate'. For a simple tool, the definition is adequate but not sufficient.

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%, so both envId and isForward are already documented in the schema, including the default of false. The description adds nothing about format or edge cases beyond what the schema states, so the 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?

The description names a specific verb+resource: 'Navigate browser history (back/forward)'. It is clear about the operation, but it does not explicitly differentiate itself from the sibling tool 'navigate' or state the relationship between history traversal and direct navigation.

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?

The description implies usage (replaying history back or forward), but it offers no when-to-use or when-not-to-use guidance, no mention of prerequisites such as an existing session or populated history, and no named alternative such as 'navigate' for directly going to a URL.

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