Skip to main content
Glama
Sign In
gecko-mcp

gecko-mcp

by Frumane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

hover

Move the mouse pointer over a web page element using a CSS selector or ref. The view scrolls automatically to the element. Targets the active tab by default, or a specific browser tab.

Instructions

Hover the mouse over an element (CSS selector or ref). Auto-scrolls into view. Active tab unless browserId given.

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": "hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorNoCSS selector.
refNoFingerprint ref from snapshot.
browserIdNoTarget tab. Defaults to active.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.4

TDQS

A4/5.0
Behavior4/5

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

Annotations indicate non-destructive, non-read-only nature. Description adds auto-scroll behavior and default tab targeting, providing useful behavioral context beyond annotations.

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 concise sentences front-load core action and key modifiers (auto-scroll, tab targeting). No superfluous content.

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?

Covers essential behavior for a hover tool with 3 optional parameters. No output schema, but hover is simple enough that completeness is adequate. Minor omission: no mention of potential side effects like triggering tooltips.

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 covers 100% of parameter descriptions. The tool description adds minimal extra meaning (e.g., highlights ref as fingerprint), but does not significantly enhance understanding beyond schema.

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?

Clearly states 'Hover the mouse over an element' and specifies valid identifiers (CSS selector or ref). Distinguishes from sibling tools like click or move_cursor by focusing on hover action and auto-scrolling behavior.

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?

Implies usage for hovering, but lacks explicit when-not-to-use or alternative tool guidance. No mention of prerequisites or context where hover might be inappropriate.

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

Deploy Server

Other Tools