Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_session_history

Navigate browser session history by going back, forward, or to a specific index, and retrieve history entries for a given environment.

Instructions

Navigate session history (back/forward/go to specific index)

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

Input Schema

NameRequiredDescriptionDefault
envIdYesEnvironment ID for the browser environment to operate.
indexNoHistory index to navigate to (required for go action)
actionNoAction type: back, forward, go, get_entries, get

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. It never states that back/forward/go alter the live page state (a mutation of browser position), whether navigation waits for load, or what get_entries returns; only the surface concept of history traversal is conveyed.

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 tight sentence plus a parenthetical that front-loads the three navigation modes. Nothing is wasted, though the brevity leaves the enum's read actions unmentioned.

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 three-parameter, no-annotation, no-output-schema tool, the description is thin: it covers navigation but not the get/get_entries read path, and gives no return-value or state-effect context. The high schema coverage covers parameters, but behavioral completeness is left short.

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 the enum and the index parameter are already documented in structured fields. The description adds marginal reinforcement by tying "specific index" to the go action, but nothing beyond that.

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 pairs the verb "Navigate" with the specific resource "session history" and enumerates the modes (back/forward/go to index). It does not distinguish itself from the sibling chrome_history or from navigate, and it omits the two read actions (get_entries, get) present in the schema, so an agent cannot fully separate this tool from its neighbours.

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 on when to use this versus chrome_history, navigate, or any other browsing tool. It also never signals when the non-navigational actions (get, get_entries) are the right choice, so the agent must infer usage from the enum alone.

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