Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_mouse_control

Controls mouse and touch events (move, click, down, up, wheel) in a browser environment to automate interactions.

Instructions

Control mouse and touch actions including move, click, wheel, etc.

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>",
      "action": "<action>"
    },
    "name": "chrome_mouse_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of clicks to perform
delayNoDelay between actions in milliseconds
envIdYesEnvironment ID for the browser environment to operate.
touchNoWhether to use touch events instead of mouse events
actionYesAction to perform: move, click, down, up, wheel.
buttonNoMouse button to use: left, right, middleleft
deltaXNoHorizontal scroll delta for wheel action
deltaYNoVertical scroll delta for wheel action
selectorNoCSS selector for the element to perform action on. Either selector or coordinates must be provided.
coordinatesNoCoordinates to perform action at (relative to viewport). If provided, takes precedence over selector.

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 informational burden, yet it discloses almost nothing beyond the schema: not whether actions mutate page state, whether elements are auto-scrolled into view, what happens on failure, or how touch mode differs. The only added word, 'touch', is already represented by the touch parameter.

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 short sentence with the core purpose front-loaded and no filler. The trailing 'etc.' is the only wasted token, though brevity here comes at the cost of substance rather than being efficient packaging of rich content.

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 ten-parameter, nested-object, side-effecting browser interaction tool with no annotations and no output schema, this one sentence is far too thin. An agent still cannot tell which action/parameter combinations are valid (e.g., deltas only for wheel, coordinates ignored for wheel) or what the tool does to the page.

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%, including the selector-vs-coordinates precedence and wheel-delta notes, so the schema does the heavy lifting. The description adds no meaning beyond it, which is the baseline-3 case when the schema fully documents the ten parameters.

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 gives a specific verb ('Control') and resource ('mouse and touch actions') and enumerates the action families (move, click, wheel) that match the action enum. It is clear what the tool does, but it does not distinguish itself from siblings such as chrome_click_element or chrome_get_interactive_elements, and the trailing 'etc.' weakens the scope statement.

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 use this tool rather than chrome_click_element, chrome_keyboard, or a selector-based alternative. No preconditions (element visibility, focus, session state) or exclusions are stated, leaving the agent to infer usage entirely.

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