Skip to main content
Glama

Click

click

Dispatches a mouse button press at specified coordinates, clamped to the active window boundaries so GUI automation stays within the target window.

Instructions

Dispatches a mouse click clamped within the active window boundaries.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
pidNo
buttonNoleft

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, non-open-world action. The description adds one genuinely useful behavioral detail — coordinates are clamped to the active window — but says nothing about whether the click blocks, whether it raises/focuses the window first, or what happens if no window is active.

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?

A single front-loaded sentence with no filler; the constraint appears immediately after the action. It is efficient, though efficiency here shades into under-specification rather than crispness.

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 a four-parameter input tool with zero schema description coverage and no output schema, one sentence is not enough. Missing coordinate-space semantics, pid targeting, button options, and post-click behavior leave real ambiguity about how to invoke it correctly.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description carries the full burden. It only hints that x/y are window-relative via "clamped within the active window boundaries"; it never explains the coordinate origin, what `pid` targets, or what values `button` accepts beyond the schema default of "left".

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 resource ("Dispatches a mouse click") plus a scoping constraint (clamped to the active window). It does not differentiate itself from siblings like double_click or right_click, and the presence of a `button` parameter muddies the boundary with right_click.

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 guidance on when to use this versus double_click, right_click, or interact_with_node, nor any prerequisite such as the target window needing focus. The agent must infer all selection logic from the sibling names alone.

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