Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_history

Retrieve and search Chrome browsing history for a specified browser environment, filtering entries by text and limiting results for focused review.

Instructions

Retrieve and search browsing history from Chrome

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText to search for in history URLs and titles. Leave empty to retrieve all history entries within the time range.
envIdYesEnvironment ID for the browser environment to operate.
maxResultsNoMaximum number of history entries to return. Use this to limit results for performance or to focus on the most relevant entries. (default: 100)

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?

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about whether an environment must be active, whether history is read from the local Chrome profile, how results are ordered or paginated, or what the response looks like. For a retrieval tool with zero annotation coverage this is a substantive gap.

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 compact sentence with no wasted words and the core action front-loaded. It is efficient, though the terseness leaves it without any structure for guidance or caveats.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only source of behavioral context, and it supplies none beyond purpose. An agent still cannot tell what constraints, ordering, or return shape to expect.

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 all three parameters (text, envId, maxResults) are already documented in the input schema, which sets the baseline at 3. The description itself adds no parameter meaning beyond 'search browsing history', so it neither helps nor hurts.

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?

States a specific verb and resource: 'Retrieve and search browsing history from Chrome'. An agent can tell it reads/search browser history, but nothing distinguishes it from the sibling chrome_session_history, so the sibling-differentiation criterion for a 5 is unmet.

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 or when-not-to-use guidance, no mention of prerequisites such as an active browser environment or session, and no routing to chrome_session_history or chrome_get_web_content for related needs. Only the purpose sentence implies usage.

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