Skip to main content
Glama

desktop_click

Click a UI element on your desktop via the accessibility press action, resolving a snapshot reference before acting so agents can trigger buttons, links, and menu items reliably.

Instructions

agent-desktop click: Click element via accessibility press action

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_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

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 entire behavioral burden, and it largely does not. It does disclose the underlying mechanism (accessibility press rather than synthesized mouse events), which is valuable, but says nothing about side effects, whether the element is scrolled into view, focus requirements, or failure behavior.

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?

An eight-word sentence with zero filler and the mechanism placed immediately after the verb. It is efficient, though the brevity edges toward under-specification rather than optimal density.

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?

With two well-documented parameters and no output schema, the definition is callable as-is, but for a side-effecting UI action with zero annotation coverage it is thin on consequences and failure modes. The schema's timeout wording about terminal failures is the only behavioral detail, and it lives outside the description.

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 and timeout_ms are already well documented in the schema, making 3 the baseline. The description adds only the implicit hint that ref_id targets an accessibility element; it contributes nothing about the timeout parameter.

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 (click) and resource (element) plus the mechanism (accessibility press action), which meaningfully distinguishes it from coordinate-based siblings like desktop_mouse_click. It stops short of naming an alternative, so it is clear but not fully sibling-differentiated.

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?

Provides no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative. An agent must infer from 'via accessibility press action' that this works on snapshot refs rather than screen coordinates.

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