Skip to main content
Glama
fixed-width

glass

by fixed-width
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust

glass_click

Click a window-relative point using x/y coordinates, optionally setting mouse button, click count, or held modifiers. Use for single GUI interactions.

Instructions

Click a window-relative point, optionally with a button, click count and held modifiers. For 2+ known steps, use glass_do.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesClick x in window-relative pixels.
yYesClick y in window-relative pixels.
countNoClick count (default 1, range 1 through 10); 2 double-clicks.
buttonNo"left" (default), "right", or "middle".
modifiersNoHeld modifiers, e.g. ["ctrl", "shift"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.8.0
    • changedInput schema / properties / count / description
      Previous value: -"Consecutive clicks at this point (default 1, valid range 1 through 10); pass 2 for a\ndouble-click."New value: +"Click count (default 1, range 1 through 10); 2 double-clicks."
    • changedInput schema / properties / modifiers / description
      Previous value: -"Modifier keys to hold during the action, e.g. [\"ctrl\"] or [\"ctrl\",\"shift\"] for multi/range-select."New value: +"Held modifiers, e.g. [\"ctrl\", \"shift\"]."
    • changedInput schema / properties / x / description
      Previous value: -"Click point x, window-relative — 0 is the window's left edge, not the screen's."New value: +"Click x in window-relative pixels."
    • changedInput schema / properties / y / description
      Previous value: -"Click point y, window-relative — 0 is the window's top edge, not the screen's."New value: +"Click y in window-relative pixels."
  2. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / count / description
      Previous value: -"Consecutive clicks at this point (default 1); pass 2 for a double-click."New value: +"Consecutive clicks at this point (default 1, valid range 1 through 10); pass 2 for a\ndouble-click."
    • addedInput schema / properties / count / maximum
      Added value: +10
    • changedInput schema / properties / count / minimum
      Previous value: -0New value: +1
  3. Changed4 schema fields changedv1.2.0
    • addedInput schema / properties / count / description
      Added value: +"Consecutive clicks at this point (default 1); pass 2 for a double-click."
    • addedInput schema / properties / x / description
      Added value: +"Click point x, window-relative — 0 is the window's left edge, not the screen's."
    • addedInput schema / properties / y / description
      Added value: +"Click point y, window-relative — 0 is the window's top edge, not the screen's."
    • removedInput schema / title
      Removed value: -"ClickArgs"
  4. Addedv1.0.3

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already convey readOnlyHint=false and destructiveHint=false. The description adds the useful window-relative coordinate context, but it does not disclose further behavioral details beyond what a click operation implies, and the optional button/count/modifiers mostly restate schema properties.

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?

The description is two sentences with no filler: the primary action is front-loaded, optional parameters are summarized in one clause, and the alternative tool is routed in the second sentence. Every sentence earns its place.

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

Completeness5/5

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

For a simple click tool, the description plus full parameter schema covers the coordinate space, optional arguments, and multi-step routing via glass_do. No output schema exists, but a return-value explanation is not essential for a click operation.

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 100%, with each parameter already described in the input schema. The description's mention of button, click count, and modifiers adds no new meaning beyond those schema descriptions, so the baseline score of 3 is appropriate.

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?

The description uses a specific verb ('Click') and a clear resource ('a window-relative point'), and it lists the optional inputs. It also distinguishes itself from glass_do, which is the main sibling an agent might confuse it with.

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

Usage Guidelines5/5

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

The description explicitly states a routing rule: 'For 2+ known steps, use glass_do.' This tells the agent when to choose an alternative, leaving the single-click case clearly as the context for this tool.

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

Deploy Server

Other Tools