Skip to main content
Glama
MathiasPaulenko

WaveXisMCP

by MathiasPaulenko
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

wavexis_hover

Hover over a CSS-selected element to trigger mouseover/mouseenter events, revealing tooltips or menus without clicking. Use it to interact with hover-dependent UI.

Instructions

Hover over an element matching a CSS selector.

Use wavexis_click to actually activate an element; hover only moves the cursor without clicking.

Side effects: Moves the mouse cursor over the target element, firing mouseover/mouseenter events that may reveal tooltips or menus. Returns: JSON string with keys: 'status' ('ok'/'error'). On error also 'error', 'tool', 'type', 'message', 'suggestion' (all str).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changedv1.6.24
    • addedInput schema / $defs / HoverInput / properties / backend / description
      Added value: +"Backend: 'cdp', 'bidi', or 'auto'"
    • addedInput schema / $defs / HoverInput / properties / backend / enum
      Added value: +[
+  "cdp",
+  "bidi",
+  "auto"
+]
    • addedInput schema / $defs / HoverInput / properties / headless / description
      Added value: +"Run browser in headless mode"
    • addedInput schema / $defs / HoverInput / properties / selector / description
      Added value: +"CSS selector for the target element"
    • addedInput schema / $defs / HoverInput / properties / selector / minLength
      Added value: +1
    • addedInput schema / $defs / HoverInput / properties / session_id / description
      Added value: +"Active session ID. If omitted, a stateless session is created for this call."
    • addedInput schema / $defs / HoverInput / properties / url / description
      Added value: +"URL to navigate to (required without session_id)"
    • addedInput schema / $defs / HoverInput / properties / wait_timeout / description
      Added value: +"Timeout in ms for wait conditions"
    • addedInput schema / $defs / HoverInput / properties / wait_timeout / maximum
      Added value: +300000
    • addedInput schema / $defs / HoverInput / properties / wait_timeout / minimum
      Added value: +1000
  2. First observedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

Annotations indicate readOnlyHint false and destructiveHint false, which are consistent with a hover operation. The description adds value by detailing side effects: moving the mouse cursor and firing mouseover/mouseenter events that may reveal tooltips. No contradictions or missing critical behaviors.

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 description is extremely concise, with no wasted words. It front-loads the purpose, then distinguishes from sibling, lists side effects, and specifies return format. Every sentence serves a clear purpose.

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

Completeness4/5

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

Given the simplicity of the hover operation, the description is sufficiently complete. It covers purpose, comparison to click, side effects, and return format. However, it does not explain session management implications, but that is partially covered by sibling tools and schema. Overall, very good.

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?

The input schema provides descriptions for each parameter, so the schema already handles parameter meaning. The tool description only mentions the CSS selector and does not add additional context for other parameters (url, backend, etc.). Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Hover over an element matching a CSS selector' and explicitly distinguishes from wavexis_click by noting that hover only moves the cursor without clicking. This differentiates it from its sibling tool effectively.

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?

The description explicitly references wavexis_click as the alternative for activating an element, providing clear when-to-use guidance. It does not explicitly list when not to use, but the context is sufficient for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MathiasPaulenko/wavexis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server