Skip to main content
Glama

Double Click

double_click

Sends a double-click at specified x/y coordinates within the active window boundaries, enabling GUI automation and testing on Wayland.

Instructions

Dispatches a double-click within the active window boundaries.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "double_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
pidNo
buttonNoleft

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, openWorldHint=false and idempotentHint=false, so the agent knows this is a non-destructive, local interaction; the description's 'active window boundaries' constraint is consistent with openWorldHint=false and adds real scoping value. However, nothing is said about cursor movement, focus requirements, or double-click timing, which are the traits an agent actually needs for an input-synthesis tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler, but that brevity comes at the cost of substance rather than through efficiency. Front-loading is fine; there simply is very little 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 4-parameter input-synthesis tool with zero schema description coverage and no output schema, the description should explain coordinate space, the meaning of pid, and any focus/cursor side effects. None of that is present, so an agent must infer behavior from the parameter names alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description explains none of the four parameters. It implies x/y are window-relative coordinates, but the 'pid' parameter (default null) and the 'button' default of 'left' are entirely unaddressed, and coordinate origin/bounds are left to guesswork.

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 ('Dispatches a double-click') plus a scope ('within the active window boundaries'), which lets an agent distinguish it from click/right_click by the action itself. It never names siblings or contrasts behavior, so it falls short of 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?

No guidance on when to prefer a double-click over click plus a follow-up action, no prerequisites such as whether the target window must be focused, and no mention of alternatives like interact_with_node for UI-element targets. The only hint is the implicit 'active window' constraint.

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