Skip to main content
Glama

click_xy

Destructive

Click at native screen coordinates on a remote Windows PC. Use when no UI element target exists to simulate a mouse click at precise pixel positions.

Instructions

Click at native screen coordinates (0…native_width-1, 0…native_height-1 from observe). Last resort when no suitable UIA target exists — prefer click_target. Never use JPEG/downscaled pixel coords. Side effect: real mouse click on the remote desktop.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesNative X (0…native_width-1)
yYesNative Y (0…native_height-1)
buttonNoMouse button (default left)
doubleNoIf true, double-click
session_idYesActive session id
Behavior5/5

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

Discloses the side effect of a real mouse click on the remote desktop, which adds value beyond the destructiveHint annotation. No contradiction with annotations.

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?

Two sentences with zero wasted words. Every sentence provides critical information (purpose, usage, warnings).

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 click tool with 5 parameters, all well-described in schema, the description covers when to use, side effects, and coordinate system. No output schema needed.

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%, but the description adds important context about native coordinates and the prohibition of JPEG/downscaled coords, which enhances understanding beyond the schema.

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 clearly states the tool clicks at native screen coordinates and distinguishes it from the sibling click_target by noting it's a last resort when no UIA target exists.

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?

Explicitly says to prefer click_target when possible and warns against using JPEG or downscaled pixel coordinates, providing clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/glasswarp/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server