Skip to main content
Glama

desktop_triple_click

Triple-clicks a resolved desktop UI element to select text or trigger multi-click actions; returns POLICY_DENIED when physical input is disabled.

Instructions

agent-desktop triple-click: Triple-click element; returns POLICY_DENIED when physical input is disabled

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_triple_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.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful trait: a POLICY_DENIED failure when physical input is disabled. However, it says nothing about the side effect of triple-clicking (typically selecting a paragraph/line), focus requirements, or what a success response contains — significant gaps for an input-injecting tool.

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?

One compact, front-loaded sentence with no filler. The 'agent-desktop triple-click:' prefix duplicates the tool name and could be dropped, which is the only wasted text.

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 2-parameter, no-annotations, no-output-schema tool, the definition covers purpose and one error condition but omits return shape and confirmable side effects. Adequate but with clear gaps an agent would want filled.

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

Parameters4/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 documented in detail; the description adds only that ref_id denotes an 'element'. Baseline 3 is met and the element framing is a slight lift.

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+resource: 'Triple-click element.' The name-plus-verb pairing makes it distinguishable from desktop_click and desktop_double_click by the click count itself, though the description never names those siblings or contrasts the effects.

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 guidance at all: nothing says why an agent would triple-click rather than use desktop_click/desktop_double_click, nor what state (focus, open window, element type) must hold beforehand. Usage is only implied by the tool name.

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