ReMCP

Computer Scroll

computer_scroll

Use this to scroll the native desktop viewport or an identified UI region by a bounded direction or delta. It moves the visible viewport and does not edit document contents.

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.
`delta`	No	Alias for delta_y.
`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.
`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.
`delta_x`	No	Horizontal scroll delta; positive means right.
`delta_y`	No	Vertical scroll delta; positive means down.
`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.
`direction`	No	Human-readable scroll direction used with wheel_times instead of explicit deltas.
`window_id`	No	Top-level window id returned by list_windows when target=window.
`wheel_times`	No	Number of 120-unit wheel steps for direction; 1..50.
`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

A4.7/5.0

Behavior5/5

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

It adds crucial behavioral constraints beyond the schema and annotations by explicitly stating that it 'moves the visible viewport' and, critically, 'does not edit document contents.' This prevents misuse and defines the mutation type.

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 brief and highly efficient. It front-loads the primary function and immediately follows up with the necessary behavioral constraint, maximizing information density without filler.

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?

Given the extreme parameter complexity (22 parameters), this description provides the perfect, concise high-level summary of the tool's functional scope. It informs the agent that the action is visual navigation, making the use of the specific targeting parameters meaningful.

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?

The schema provides high coverage (100%), but the description adds semantic value by defining the *nature* of the parameter action: scrolling the 'native desktop viewport' or an 'identified UI region,' providing the conceptual framework for how the numerous targeting parameters should be used.

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 purpose is stated with high precision: scrolling the 'native desktop viewport or an identified UI region'. This is an active, specific verb (scroll) applied to defined resources (desktop/UI region), clearly distinguishing it from content editing.

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

Usage Guidelines4/5

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

While the description doesn't explicitly contrast itself with every sibling (e.g., `browser_scroll`), it clearly defines its operational scope (viewport movement vs. content editing), guiding the agent on *when* this tool is the correct choice for a visual shift operation.

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?