Skip to main content
Glama
Sign In
neko-browser

neko-browser

by aliksir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

neko_hover

Hover over elements by index to activate tooltips and dropdown menus via mouseover events.

Instructions

Hover over an element by index. Triggers mouseover events (for tooltips, dropdown menus, etc.).

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": {
      "index": "<index>"
    },
    "name": "neko_hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYesElement index from neko_get_state

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description must fully disclose behavior. It states the primary effect (mouseover events) but omits details on failure modes, prerequisites (e.g., element visibility), or potential side effects. This is adequate but not comprehensive.

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 two sentences, front-loaded with the main action, and contains no extraneous information. Every word is useful.

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 tool's simplicity (one parameter, no output schema, no annotations), the description covers the essential aspects: what it does and when to use it. It could mention return values (if any) but is largely sufficient.

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 description explains that the 'index' parameter is 'from neko_get_state', adding context beyond the input schema's description. With 100% schema coverage, baseline is 3, and the extra context justifies a 4.

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 the action ('Hover'), the target ('element by index'), and the effect ('triggers mouseover events'), with examples of use (tooltips, dropdown menus). It effectively distinguishes from sibling tools like neko_click or neko_double_click.

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 gives context for when to use the tool (to trigger hover-dependent UI elements) but does not explicitly state when not to use it or mention alternatives. However, the sibling list and tool names imply distinct use cases, so the guidance is clear.

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