Glasswarp

input.click_xy

Destructive

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

Input Schema

TableJSON Schema

Name	Required	Description
`x`	Yes	Native X (0…native_width-1)
`y`	Yes	Native Y (0…native_height-1)
`button`	No	Mouse button (default left)
`double`	No	If true, double-click
`session_id`	Yes	Active session id

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes	False when the tool failed
`message`	Yes	Human-readable result for the agent

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations (destructiveHint, openWorldHint), description adds 'Side effect: real mouse click on the remote desktop' and clarifies coordinate system usage.

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 focused sentences, no redundant words, front-loaded with core purpose and critical usage guidance.

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?

Covers when to use, coordinate system, side effects, and alternatives; output schema handles return values; sufficient for a tool with good annotations.

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 description adds valuable context about native coordinates and their origin from screen.observe, enhancing schema meaning.

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?

Clearly states 'Click at native screen coordinates' and distinguishes from sibling tool 'input.click_target' by specifying it's a last resort.

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 'Last resort when no suitable UIA target exists — prefer input.click_target' and warns against using JPEG/downscaled pixel coords.

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

All Glasswarp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.