Skip to main content
Glama

hands_click

Clicks browser elements by ref or visible text; dangerous buttons require fresh reflex_ask approval for one click.

Instructions

Click a browser element by ref (btn_1/input_2/link_3) or unique visible text. Dangerous buttons require a fresh reflex_ask() approval — one approval, one click.

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": {
      "target": "<target>"
    },
    "name": "hands_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations at all, the description must carry the full behavioral burden. It usefully discloses the approval gate and the "one approval, one click" non-reusability rule, but says nothing about failure behavior (target not found), whether the click waits for navigation, or what the call returns.

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

Conciseness5/5

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

Two short sentences, each earning its place: the first defines targeting, the second defines the safety gate. The critical constraint is front-loaded rather than buried.

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

Completeness4/5

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

For a one-parameter click tool with no output schema and no annotations, the definition covers the two things an agent must know: how to address the element and when an approval is required. Only return-value and error semantics are absent, which is a modest gap given the tool's simplicity.

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 0% for the single `target` parameter, so the description must compensate — and it does, explaining both ref syntax (btn_1/input_2/link_3) and the fallback of unique visible text. The remaining gap is what constitutes "unique" or what happens on ambiguous matches.

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 plus resource ("Click a browser element") and enumerates accepted target forms (btn_1/input_2/link_3 or unique visible text). The word "browser" implicitly separates it from desktop_click, but no sibling is named explicitly, so the differentiation is inferential rather than stated.

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 states a real prerequisite — dangerous buttons need a fresh reflex_ask() approval — which tells the agent when an extra step is mandatory. However, it never says when to prefer hands_click over hands_press, desktop_click, or hands_batch, so the routing decision is left to inference.

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