Skip to main content
Glama
Sign In
Antigravity Desktop MCP

Antigravity Desktop MCP

by silas-ouyang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

desktop_move

Move the mouse cursor to absolute coordinates or by relative delta to trigger hover tooltips, follow UI elements, or control pointer-locked canvases.

Instructions

Move the mouse cursor to absolute/frame-projected (x, y) or by relative delta (dx, dy) for hover tooltips or pointer-locked canvases.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "desktop_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
dxNo
dyNo
from_frameNo
allow_windowsNo
allow_activateNo
verify_contentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

The annotations already establish that this is a non-destructive, non-read-only, closed-world operation. The description adds the coordinate modes but does not explain consequential parameters like allow_activate, allow_windows, or verify_content, nor does it mention side effects such as hover triggering or window activation.

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 definition is a single front-loaded sentence that states the action and coordinate modes without unnecessary wording. Every phrase contributes to understanding how to invoke the tool.

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?

For an eight-parameter desktop automation tool with no output schema and no schema descriptions, the description is too thin. It covers the basic coordinate inputs but omits the behavior and purpose of the remaining flags that affect activation, window handling, and content verification.

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?

The description explains x, y, dx, dy, and frame projection, which helps with the coordinate parameters. With 0% schema description coverage across eight parameters, it leaves allow_windows, allow_activate, and verify_content completely undocumented, so it only partially compensates for the schema gap.

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 gives a specific verb and resource: moving the mouse cursor. It clearly distinguishes absolute/frame-projected coordinates from relative deltas, though it does not explicitly differentiate itself from sibling tools such as desktop_drag or desktop_click.

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?

It provides implied use cases: hover tooltips and pointer-locked canvases. However, it does not state when not to use this tool or name alternatives for other cursor-based interactions.

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

Deploy Server

Other Tools