Skip to main content
Glama

click

Simulate a mouse press on desktop GUI targets via coordinates or element selector; defaults to dry-run to preview the target without interacting.

Instructions

Click by coordinates OR by element selector. Default dry_run=true (returns target without clicking).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
hwndNo
regexNo
budgetNohow many times this call may drive the user's pointer (0 = never, the default). Semantic rungs are free; only the pixel rung is paid for
buttonNoleft
doubleNo
methodNohow the click is delivered: auto walks invoke -> message -> pixel and stops at the first rung that works; pixel/foreground ask for the pointer out loudauto
dry_runNo
control_typeNo
name_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the most important safety trait — dry_run defaults to true and returns the target without clicking — which is real value the schema alone doesn't spell out. However, it says nothing about escalation behavior across the 'auto' method rungs, pointer-driving side effects, failure modes, or how 'returns target' is shaped.

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 tight sentences with the targeting options front-loaded and the default-behavior caveat second; nothing is wasted. It is arguably too terse for an 11-parameter tool, but that is a completeness problem rather than a verbosity one.

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

Completeness2/5

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

For an 11-parameter, zero-annotation, no-output-schema mutation tool, the description is far too thin. An agent learns the targeting modes and the dry_run default but not which parameters belong to which mode, what a successful call returns, or what the interaction model costs.

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?

With 11 parameters and only 18% schema description coverage, the description must compensate, and it only clarifies two idea-groups: coordinate targeting vs. element-selector targeting, plus the dry_run default. The semantics of hwnd, regex, budget, control_type, name_contains, button, and double are left entirely to the schema.

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 and the two mutually exclusive targeting modes ('by coordinates OR by element selector'), which tells an agent this is a UI-click primitive. It stops short of distinguishing itself from siblings such as click_by_id or browser_click, so an agent cannot tell which click tool to pick without opening schemas.

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?

No when-to-use or when-not-to-use guidance and no mention of prerequisites, target requirements, or alternatives. The only decision guidance is the implicit 'coordinates OR selector' choice, which the schema's parameter set already implies.

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