Argus

Overview Schema Source Related Servers Discussions Admin

Hover over Element by Description

hover_what

Hover a uniquely matching element, or a list row by its exact text, with a real pointer to reveal tooltips, hover menus or hover-only controls. Returns the observation taken while hovering, so revealed controls are targetable.

Instructions

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": {
      "description": "<description>"
    },
    "name": "hover_what"
  }
}

Input Schema

Name	Required	Description	Default
`description`	Yes

Output Schema

Name	Required	Description	Default
`data`	No
`run_id`	Yes
`stages`	No
`status`	Yes
`recovery`	No
`operation`	Yes
`error_code`	Yes
`session_state`	Yes
`schema_version`	No
`progress_omitted`	No
`progress_delivery_failed`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.10.0Oct 26, 2026
- removedInput schema / properties / description / title
```
Removed value: -"Description"
```
- removedInput schema / title
```
Removed value: -"hover_whatArguments"
```
Changed12 schema fields changedOct 26, 2026
- removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
- removedOutput schema / properties / error_code / title
```
Removed value: -"Error Code"
```
- removedOutput schema / properties / operation / title
```
Removed value: -"Operation"
```
- removedOutput schema / properties / progress_delivery_failed / title
```
Removed value: -"Progress Delivery Failed"
```
- removedOutput schema / properties / progress_omitted / title
```
Removed value: -"Progress Omitted"
```
- removedOutput schema / properties / recovery / title
```
Removed value: -"Recovery"
```
- removedOutput schema / properties / run_id / title
```
Removed value: -"Run Id"
```
- removedOutput schema / properties / schema_version / title
```
Removed value: -"Schema Version"
```
- removedOutput schema / properties / session_state / title
```
Removed value: -"Session State"
```
- removedOutput schema / properties / stages / title
```
Removed value: -"Stages"
```
- removedOutput schema / properties / status / title
```
Removed value: -"Status"
```
- removedOutput schema / title
```
Removed value: -"AgentResult"
```

Changed14 schema fields changedv0.5.2Oct 26, 2026

addedOutput schema / properties / data

Added value: +{
+  "additionalProperties": true,
+  "title": "Data",
+  "type": "object"
+}

addedOutput schema / properties / error_code

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Error Code"
+}

addedOutput schema / properties / operation

Added value: +{
+  "title": "Operation",
+  "type": "string"
+}

addedOutput schema / properties / progress_delivery_failed

Added value: +{
+  "default": false,
+  "title": "Progress Delivery Failed",
+  "type": "boolean"
+}

addedOutput schema / properties / progress_omitted

Added value: +{
+  "default": 0,
+  "title": "Progress Omitted",
+  "type": "integer"
+}

addedOutput schema / properties / recovery

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Recovery",
+  "type": "array"
+}

removedOutput schema / properties / result

Removed value: -{
-  "title": "Result",
-  "type": "string"
-}

addedOutput schema / properties / run_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Run Id"
+}

addedOutput schema / properties / schema_version

Added value: +{
+  "const": 1,
+  "default": 1,
+  "title": "Schema Version",
+  "type": "integer"
+}

addedOutput schema / properties / session_state

Added value: +{
+  "title": "Session State",
+  "type": "string"
+}

addedOutput schema / properties / stages

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Stages",
+  "type": "array"
+}

addedOutput schema / properties / status

Added value: +{
+  "enum": [
+    "completed",
+    "error"
+  ],
+  "title": "Status",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "operation",
+  "status",
+  "session_state",
+  "run_id",
+  "error_code"
+]

changedOutput schema / title

Previous value: -"hover_whatOutput"New value: +"AgentResult"

Addedv0.5.1Jul 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With readOnlyHint=false and idempotentHint=false already declaring this as a non-read, repeatable-side-effect-prone action, the description adds real context: the hover uses a real pointer and the returned observation is captured mid-hover so revealed controls can be targeted. It does not mention timeouts, failure modes, or what happens if the element is non-unique, which is the main remaining gap.

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 refined by the return-value note. No restatement of the title and nothing superfluous.

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

Completeness5/5

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

For a one-parameter tool with an output schema (so return values need not be detailed), the description covers the action, the purpose, and the key return behavior. Nothing essential to invoking it correctly is missing.

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?

The single parameter is only typed 'string' with 0% schema description coverage, so the description must carry meaning, and it does: the value must uniquely match an element, or be the exact text of a list row. It still doesn't specify the matching syntax (CSS? text? accessibility name?), which leaves ambiguity for the agent.

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?

Names a specific verb (hover) and resource (an element, or a list row matched by exact text), so the action is unambiguous. It does not explicitly distinguish itself from siblings like click_what or select_into, leaving the agent to infer the boundary.

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

Usage Guidelines4/5

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

Gives the triggering intent clearly: reveal tooltips, hover menus, or hover-only controls. It does not state when not to use it or name the sibling to pick instead for non-hover interactions, so routing still requires some inference.

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