Skip to main content
Glama

desktop_hover

Move the cursor to a target UI element or exact screen coordinates in a headed desktop session to trigger hover interactions and verify hover-dependent behavior.

Instructions

agent-desktop hover: Move cursor to element center or coordinates (requires --headed)

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_hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
xyNoAbsolute coordinates as x,y; requires --headed; write a negative value with = (--xy=-100,50)
ref_idNoElement ref to hover over; requires --headed
durationNoReserved for compatibility; positive values are rejected in stateless mode (run hover, then `wait <ms>` instead)
timeout_msNoMaximum ref-resolution and transient-actionability wait in milliseconds; terminal failures return immediately

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the headed-mode requirement but does not explain side effects, whether hover triggers UI changes, stateless-mode constraints, or failure behavior.

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 description is a single front-loaded sentence with no wasted wording. The "agent-desktop hover:" prefix is slightly redundant but does not obscure the action.

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 a tool with no annotations and no output schema, the description is too thin. It omits behavioral context such as stateless-mode handling, duration rejection, timeout semantics, and what a successful hover returns.

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 description coverage is 100%, so the schema already documents xy, ref_id, duration, and timeout_ms. The description only restates the element-center/coordinates concept and adds no parameter meaning beyond the schema.

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 specific verb and resource: "Move cursor to element center or coordinates." It clearly identifies hover behavior, though it does not explicitly distinguish this from siblings like desktop_click or desktop_drag.

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?

The only guidance is the prerequisite "requires --headed." There is no explanation of when to use hover instead of click, drag, or other pointer actions, and no when-not guidance.

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