Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

navigate

Open a URL in a specified browser environment or refresh the active tab for browser automation tasks.

Instructions

Navigate to a URL or refresh the current tab 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>",
      "url": "<url>"
    },
    "name": "navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to navigate to
envIdYesEnvironment ID for the browser environment to operate.
widthNoViewport width in pixels, skip it if not needed
heightNoViewport height in pixels, skip it if not needed
newTabNoCreate a new tab to navigate to the URL or not. Defaults to false
refreshNoRefresh the current active tab instead of navigating to a URL. When true, the url parameter is ignored. Defaults to false

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, yet it omits the important traits: whether navigation blocks until the page loads, whether the current tab's state is discarded, what happens on failure (timeout, bad URL), and what the call returns. The refresh/newTab semantics it implies are already spelled out verbatim in the schema, so little is added.

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 filler, and the two modes (navigate vs refresh) are stated up front. It is efficient but so terse that it borders on under-specification rather than optimal density.

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?

For a 6-parameter browser-control tool with no annotations and no output schema, the description should say what the agent gets back and what state the environment is left in. It says neither, leaving the caller unable to predict the result of a navigation.

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 every parameter (url, envId, width, height, newTab, refresh) is already documented, including defaults and the note that url is ignored when refresh is true. The description adds no format, precedence, or interaction detail beyond that, which matches the baseline 3.

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+resource pair ('Navigate to a URL') and adds the secondary mode ('refresh the current tab'), plus the scope 'in the browser environment'. It is clear what the tool does, but it gives no differentiation from the many chrome_* siblings that also act on the browser.

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 guidance on when to choose this over alternatives such as chrome_session_history or chrome_get_web_content, and no prerequisites are mentioned (e.g., that an existing browser environment envId is required). The reader must infer from the parameter names that navigation is a precondition for other browser actions.

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