ReMCP

Computer Type

computer_type

Destructive

Use this to enter user-provided text into a focused or identified native desktop control, optionally clearing its previous value. First confirm the target from the current UI; never type passwords or private data into an unverified field.

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.
`text`	Yes	Unicode text to enter for action=type, or text used by multi_edit.
`clear`	No	For action=type, clear the current semantic/browser value before inserting text when supported.
`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.
`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.8/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotency; the description adds meaningful context by noting the optional clearing of previous values and the safety rule about unverified fields. It stops short of explaining what happens when no control is focused or how targeting fallbacks resolve.

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, front-loaded with the action and followed by the safety constraint. No redundancy and nothing padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 19 params fully described in schema and an output schema present, the description only needs to cover intent and hazards, which it does. The one gap is not addressing targeting fallback behavior (auto vs coordinates vs OCR) when no field is focused.

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%, so the schema already documents all 19 parameters in detail. The description only alludes to targeting ('focused or identified') and the clear option, adding little beyond what the schema spells out.

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 (enter text) and resource (native desktop control), and the word 'native desktop' implicitly distinguishes it from browser_type. It does not explicitly name its closest siblings (type_text, computer_set_value, keyboard), so differentiation is implied rather than stated.

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?

Provides a precondition ('first confirm the target from the current UI') and a safety boundary (no passwords/private data in unverified fields), which is useful. However, it never says when to pick this over browser_type, type_text, computer_set_value, or computer_multi_edit, so alternative routing is left to inference.

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?