Skip to main content
Glama

desktop_double_click

Physically double-clicks a resolved desktop UI element using its snapshot reference to trigger the element's default action, such as opening a file or folder.

Instructions

agent-desktop double-click: Physically double-click element; requires --headed

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": {
      "ref_id": "<ref_id>"
    },
    "name": "desktop_double_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
ref_idYesQualified ref from snapshot (@<snapshot_id>:eN)
timeout_msNoMaximum ref-resolution and transient-actionability wait in milliseconds; terminal failures return immediately

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden. 'Physically double-click' usefully implies synthesized OS-level input and the --headed requirement is real operational context, but it says nothing about focus/cursor movement, what happens on ref-resolution failure or timeout, or the side effects a double-click may trigger (opening files, activating items).

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?

Two clauses, front-loaded with the action, no filler. It is efficient, though borderline under-specified rather than intentionally terse.

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

Completeness3/5

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

For a two-parameter action tool with full schema coverage and no output schema, the essentials (what it does, the headed prerequisite) are present. It still leaves the agent without failure behavior, focus requirements, or guidance against neighboring click variants.

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 ref_id (qualified @<snapshot_id>:eN ref) and timeout_ms are already fully documented in the schema. The description adds no additional meaning about ref format or timeout semantics, 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 specific verb ('double-click') and resource ('element'), and 'Physically' signals that real input events are dispatched. It implicitly distinguishes itself from desktop_click and desktop_triple_click by the operation name, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives one hard prerequisite ('requires --headed'), which is genuine usage context, but offers no guidance on when to use this versus desktop_click, desktop_mouse_click, or desktop_triple_click, and no exclusions or conditions are stated.

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