Skip to main content
Glama

Hover

hover

Move the cursor to specific coordinates without clicking to trigger hover states, tooltips, or UI reveal effects in desktop apps.

Instructions

Positions cursor at coordinates without clicking to trigger hover states or tooltips.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
pidNo
duration_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

The 'without clicking' clause adds real behavioral context: this moves the pointer but performs no press, which the annotations (destructiveHint=false, readOnlyHint=false) do not convey. However, it says nothing about whether the tool waits, whether the cursor stays at the location afterward, or what the non-idempotent hint means in practice for repeated hovers.

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?

A single front-loaded sentence with zero filler; the key qualifier ('without clicking') appears early where it is most useful.

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?

Four parameters with 0% schema coverage, no output schema, and no annotations covering the pointer behavior or wait semantics. The definition should explain what duration_ms does (hover dwell time) and what pid targets, since an agent cannot infer either.

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

Parameters4/5

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

Schema description coverage is 0% and the description only loosely maps 'coordinates' to x/y, leaving pid and duration_ms unexplained, so it does not fully compensate for the 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?

States a specific verb and resource ('positions cursor at coordinates') and explicitly disambiguates from the click family with 'without clicking'. It is clearly distinguishable from siblings like click or double_click, though it does not name them.

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 an implied use case ('to trigger hover states or tooltips') that tells the agent when this is the right action, but there are no explicit exclusions or pointers to alternatives such as when to prefer inspect_ui_tree or click instead.

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