Skip to main content
Glama

pilot_hover

Hover over webpage elements using CSS selectors or element references to trigger interactive features or inspect dynamic content.

Instructions

Hover over an element by @ref or CSS selector.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYesElement ref (@e3) or CSS selector

Implementation Reference

  • The handler for the 'pilot_hover' tool, implemented within the `registerInteractionTools` function. It resolves the element reference and performs the hover action using Playwright.
    server.tool(
      'pilot_hover',
      'Hover over an element by @ref or CSS selector.',
      { ref: z.string().describe('Element ref (@e3) or CSS selector') },
      async ({ ref }) => {
        await bm.ensureBrowser();
        try {
          const resolved = await bm.resolveRef(ref);
          if ('locator' in resolved) {
            await resolved.locator.hover({ timeout: 5000 });
          } else {
            await bm.getPage().hover(resolved.selector, { timeout: 5000 });
          }
          bm.resetFailures();
          return { content: [{ type: 'text' as const, text: `Hovered ${ref}` }] };
        } catch (err) {
          bm.incrementFailures();
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
      }
    );
  • Registration of 'pilot_hover' as part of the 'standard' toolset.
    'pilot_hover', 'pilot_select_option', 'pilot_scroll', 'pilot_drag',
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action performed but omits critical browser automation details: whether it triggers mouseover/mouseenter events, blocks until completion, waits for element stability, or errors if the element is not interactable.

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 a single, front-loaded sentence of nine words with zero redundancy. Every word earns its place by conveying the action, target, and parameter mechanism.

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

Completeness3/5

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

Given this is a simple single-parameter browser action with no output schema, the description covers the basic operation adequately. However, it lacks completeness for an automation tool regarding error conditions and side effects (event triggering).

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?

Input schema has 100% description coverage, establishing a baseline of 3. The description mentions '@ref or CSS selector' which aligns with the schema documentation, but adds no additional semantic details about parameter format, validation rules, or priority if both ref types are provided.

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 clearly states the specific action ('Hover over') and target ('element') with the mechanism ('by @ref or CSS selector'). However, it does not explicitly differentiate from sibling tools like pilot_click that likely use the same selector mechanism.

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 description provides no guidance on when to use this tool versus alternatives (e.g., pilot_click for clicking vs hovering), nor does it mention prerequisites like element visibility or when hover effects are necessary.

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/TacosyHorchata/Pilot'

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