Skip to main content
Glama
Antigravity Desktop MCP

Antigravity Desktop MCP

by silas-ouyang

desktop_ui_action

Perform UI automation actions on desktop controls by reference or selector to click, set values, focus, scroll, and manage window states.

Instructions

Perform a UI Automation action on a control identified by ref (from desktop_ui) or by selector (hwnd, automation_id, name, control_type, class_name, index).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "desktop_ui_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoControl ref from desktop_ui, e.g. "s1.4".
hwndNo
nameNo
textNo
indexNo
valueNo
actionYes
prefixNo
suffixNo
instanceNo
scroll_toNo
class_nameNo
occurrenceNo
control_typeNo
automation_idNo
click_locatedNo
occurrence_modeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description adds no behavioral context beyond those annotations: it does not say which actions mutate state, whether close or set_value is risky, or what prerequisites apply.

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?

The definition is a single front-loaded sentence with no filler or repetition. It is concise, though its brevity contributes to under-specification rather than wasteful wording.

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

Completeness2/5

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

This is a complex tool with 19 possible actions, 17 parameters, no output schema, and very low schema documentation coverage. The description does not explain action semantics, return values for get_value/get_text/get_caret, or selector precedence, so it is not complete enough for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 6% for 17 parameters. The description adds some meaning for ref and the selector fields, but leaves action, value, text, prefix, suffix, instance, scroll_to, occurrence, and occurrence_mode unexplained.

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?

The description states a clear action-oriented purpose: perform a UI Automation action on a control identified by a ref or selector. It also names the source of refs (desktop_ui) and lists selector fields, but it does not distinguish this generic action dispatcher from siblings such as desktop_click or desktop_type.

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

Usage Guidelines2/5

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

It implies usage when a control ref from desktop_ui or a selector is available, but gives no explicit when-to-use guidance, no exclusions, and no comparison to alternative tools like desktop_click or desktop_type.

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