Skip to main content
Glama

click

Activate a named GUI node or an x/y point in a window, waiting for it to appear and focusing its window first. Also supports button holds, double presses, and state control.

Instructions

Click a node by its name, or a point by x and y, on the screen or inside a window. By name is the one to use: it waits up to timeout seconds for the node, raises its window and clicks its middle. When two nodes match it lists them, with where they are; when none does, the nearest names. A click gives a window the keyboard, which nothing else does on X11. hold and state, by x and y, hold the button as press_keys holds keys.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoPixels from the left
yNoPixels from the top
holdNoSeconds to keep it down before letting go
nameNoA node's name, as accessible_tree gives it: exactly, or a regex matched in full
roleNoNarrows name: exactly, or a regex
stateNoOnly press, leaving it down until a call with up; or only let go
buttonNo1 left, 2 middle, 3 right
doubleNoClick twice, as a double click
windowNoA window's title, exactly or a regex matched in full, or app=RE for its app id
sessionYesIts name, from start_session
timeoutNoBy name, seconds to wait for the node (10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false) by disclosing wait/timeout behavior, window raising, ambiguity handling (lists matching nodes, or nearest names when none match), the hold/state press-and-release semantics, and the key X11 side effect that clicking grants a window the keyboard.

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?

Front-loaded with the primary verb and the two targeting modes, and every sentence carries information. Some clauses are dense and run-on ('hold and state, by x and y, hold the button as press_keys holds keys'), which slightly hurts readability.

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 an 11-parameter tool with no output schema but full schema coverage, the description covers mode selection, timing, failure modes, and side effects. It stops short of describing what an ambiguous-match response actually returns, though it gestures at it.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: the name-vs-x/y mode split, the interactive behavior of timeout in name mode, and the hold/state pairing ('hold the button as press_keys holds keys').

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (click) and two concrete targeting modes (a node by name, or a point by x/y) on the screen or inside a window. It is immediately distinguishable from siblings like press_keys, scroll, or type_text by the action it performs.

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

Usage Guidelines4/5

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

Explicitly recommends the mode to prefer ('By name is the one to use') and explains what that mode gives you (waiting, window raising, middle-click). It does not name alternative sibling tools or state when not to use click, so it stops short of full routing guidance.

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