Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_click_element

Clicks an element by CSS selector or viewport coordinates in a browser page, with optional timeout and post-click navigation waiting.

Instructions

Click on an element in the current page or at specific coordinates

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

Input Schema

NameRequiredDescriptionDefault
envIdYesEnvironment ID for the browser environment to operate.
timeoutNoTimeout in milliseconds for waiting for the element or navigation (default: 5000)
selectorNoCSS selector for the element to click. Either selector or coordinates must be provided. if coordinates are not provided, the selector must be provided.
coordinatesNoCoordinates to click at (relative to viewport). If provided, takes precedence over selector.
waitForNavigationNoWait for page navigation to complete after click (default: 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?

No annotations are supplied, so the description carries the full burden of behavioral disclosure, yet it says nothing about side effects of clicking (navigation, form submission, downloads), what happens on timeout, or what is returned. The schema hints at waitForNavigation and timeout, but the description does not explain the behavioral consequences of a click in a live browser session.

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 or redundancy. It is efficient, though the terseness borders on under-specification for a live-browser mutation action.

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?

The tool has five parameters, a nested object, no annotations, and no output schema, so the description is the only place to learn about error behavior, navigation semantics, and session requirements. It supplies none of that, leaving an agent to infer the important runtime behavior from the schema alone.

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 including the nested coordinates object is already documented in the schema. The description only restates the selector-or-coordinates duality that the schema explains more precisely, including precedence rules, 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?

The description names a concrete verb (click) and a concrete resource (an element on the current page), and it captures both targeting modes the schema supports: CSS selector or viewport coordinates. It does not differentiate itself from related tools like chrome_mouse_control or chrome_fill_or_select, which keeps it from a 5.

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, and no named alternative. An agent cannot tell from the text when to click via selector versus raw mouse control, nor when to prefer chrome_get_interactive_elements first to discover a selector.

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