Skip to main content
Glama
Sign In
Navvi

Navvi

by fellowship-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

navvi_mousemove

Move cursor to (x,y) to trigger hover effects. Useful for web automation requiring mouse hovering without clicks.

Instructions

Move mouse to (x, y) without clicking. Useful for hover effects.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
personaNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.21.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided; description discloses that the tool moves the mouse without clicking, but does not detail other behavioral traits such as whether it triggers hover effects, waits for UI updates, or coordinates system (viewport vs. page).

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?

Single sentence efficiently conveys purpose and a key usage scenario (hover effects), with no extraneous information.

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 the lack of annotations and presence of an output schema, the description is minimal. It covers the core action but omits details like return values, error handling, and whether it triggers side effects (e.g., hover events). Adequate for a simple tool but not comprehensive.

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

Parameters2/5

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

Schema has 0% parameter description coverage; description adds no meaning to x, y (e.g., units, coordinate system) or persona, leaving ambiguity. Only the phrase 'Move mouse to (x, y)' hints at their role but insufficiently.

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?

Description clearly states action ('Move mouse'), target (x, y), and key modifier ('without clicking'), distinguishing it from click-related siblings like navvi_click.

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?

Mentions 'Useful for hover effects' which implies usage context, but lacks explicit guidance on when to use this vs. alternatives like navvi_drag or navvi_find, and no when-not-to-use conditions.

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