ReMCP

Computer Click

computer_click

Destructive

Use this to click an identified native desktop control or screen coordinate on a paired computer after inspecting the current UI. Clicking can submit forms, activate buttons or change data; use a semantic target when available.

Input Schema

Name	Required	Description
`x`	No	Virtual-desktop X coordinate used by click/scroll coordinate targeting.
`y`	No	Virtual-desktop Y coordinate used by click/scroll coordinate targeting.
`id`	No	Element id returned by ui_snapshot or ui_find. Linux ids are stable per-process accessibility paths and legacy linux:<index> ids remain accepted.
`app`	No	Limit matching to an application/process name substring when available.
`pid`	No	Limit matching to one owning process id when available.
`name`	No	Accessible name/title substring.
`role`	No	Accessible role such as Button, Edit, textbox or AXButton.
`label`	No	Compact numeric label from the most recent ui_snapshot/ui_find; useful for repeated actions without repeating names or coordinates.
`title`	No	Optional browser page title substring or top-level window title when target=window.
`button`	No	Pointer button to use for click/down/up or drag gestures.
`device`	Yes	ReMCP device id returned by list_devices. Required for every device operation.
`target`	No	Optional target type. auto prefers native accessibility, then browser DOM/CDP, then OCR/coordinates where supported. Use window for explicit top-level window focus/text/scroll targeting.
`ocr_text`	No	Visible text to find in rendered pixels for the OCR click fallback.
`selector`	No	CSS selector when the fallback target is a browser element.
`window_id`	No	Top-level window id returned by list_windows when target=window.
`browser_text`	No	Visible browser text used only to locate a DOM target; for action=type, text remains the value to enter.
`window_title`	No	Limit matching to a top-level accessibility window/frame title substring when available.
`automation_id`	No	Windows AutomationId when available.

Output Schema

Name	Required	Description	Default
`data`	No	Computer action structured result for computer_action. Stable fields are declared explicitly; platform-specific fields may be added. Large results may return truncated/bytes/preview instead of the full payload.
`text`	Yes	Concise human-readable result of the tool call.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotency; the description earns credit by concretizing what that means — clicks can submit forms, activate buttons, or change data. It does not address permissions, focus/activation side effects, or failure behavior, keeping it short of a 5.

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 tight sentence, front-loaded with purpose followed by the consequence warning and the targeting preference. No filler, though the sentence is long and could have been split for scannability.

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?

With 18 optional parameters, an output schema, and rich annotations, the description is adequate but thin: it doesn't explain the precedence among its many targeting modes (id vs label vs selector vs ocr_text) or when this tool is correct versus the overlapping ui_click/pointer_click siblings.

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 rich per-parameter descriptions (including the auto target resolution order), so the baseline is 3. The description only echoes the coordinate-vs-semantic distinction already spelled out in the x/y/id/target fields, adding no new parameter meaning.

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: click a native desktop control or screen coordinate on a paired computer. Scope is clear, but with near-duplicate siblings like ui_click, pointer_click, and browser_click in the set, it never explicitly says how it differs from them.

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?

"After inspecting the current UI" gives a usable precondition, and "use a semantic target when available" implies preferring element targeting over coordinates. However, that preference is expressed as parameter selection within this tool, not as routing guidance against ui_click/pointer_click, which an agent must still guess between.

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

All ReMCP 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.

Resources

Need Help?