ReMCP

Computer Set Range Value

computer_set_range_value

Destructive

Use this to set a numeric or range control, such as a slider, to a specific supported value on the paired desktop. Inspect the control limits first; changing it can affect application settings.

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.
`value`	No	New value for set_value, set_range_value, or select.
`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

B3.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and non-idempotence, so the safety profile is covered. The description adds real context: the target is a bounded range control and out-of-range values can affect application settings, motivating the pre-inspection advice. It does not say whether a revert is possible or what the prior value was.

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?

Two sentences, both earning their place: the action first, then the caution. No filler or redundancy. It could be tightened by naming the distinguishing sibling, but the size is well matched to a focused action tool.

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 an output schema present and rich annotations, the description needn't explain returns or safety. However, for an 18-parameter tool in a family containing ui_set_range_value, computer_set_value and browser_set_value, the omission of sibling routing leaves a real gap for correct tool selection.

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% across 18 parameters, so every parameter including value, device and target is already documented inline. The description only reinforces that value must be a supported range value, adding little syntax or format detail beyond the schema. Baseline 3 applies.

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: set a numeric/range control such as a slider to a supported value on the paired desktop. That is much more informative than the title restatement. It stops short of distinguishing itself from close siblings like computer_set_value or ui_set_range_value, which an agent must choose between.

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?

Gives one concrete prerequisite — inspect the control limits first — which is genuinely actionable. It offers no guidance on when to pick this over computer_set_value (text fields) or ui_set_range_value, so the selection logic remains implied rather than stated.

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?