Skip to main content
Glama

gui_click

Destructive

Click primary desktop screen coordinates only after explicit opt-in, enabling permission-gated GUI control for remote desktop automation.

Instructions

Click primary desktop screen coordinates; requires explicit opt-in

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": "gui_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=false, so the agent knows this is an unsafe write. The description adds two genuinely new facts beyond the annotations: the click targets only the primary screen, and an explicit opt-in is required. It still does not disclose what happens at the clicked location or whether the result is reversible, so it sits at adequate rather than rich.

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 compact sentence with the action front-loaded and the precondition trailing as a qualifier. Nothing is wasted, though it is arguably too sparse for a destructive tool.

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 two-parameter, destructive, no-output-schema tool with zero schema coverage, the definition covers the coordinate surface and the opt-in gate but leaves the concrete meaning of x/y and the consequences of clicking unstated.

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?

Schema coverage is 0%, so the description must carry the parameter burden, and it only partly does: it establishes that x/y live in the primary desktop screen coordinate space, but gives no origin point, unit (pixels?), bounds, or note that both are required.

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 (Click) and resource (primary desktop screen coordinates), which implicitly separates it from the browser_click sibling by naming the desktop screen as the target surface. It stops short of naming a sibling explicitly.

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?

The phrase 'requires explicit opt-in' signals a precondition for use, which is implied guidance, but there is no statement of when to prefer gui_click over browser_click or gui_hotkey, and no exclusions.

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