Skip to main content
Glama
Sign In
neko-browser

neko-browser

by aliksir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

neko_click

Click a browser element by its index from a previous state query or by specifying exact coordinates.

Instructions

Click an element by index (from neko_get_state) or by coordinates.

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

Input Schema

NameRequiredDescriptionDefault
xNoX coordinate
yNoY coordinate
indexNoElement index from neko_get_state

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided. Description does not disclose behavioral traits such as whether the click waits for navigation, what happens if element is not found, or if scrolling is performed. For a click action, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no waste, but it could be improved by stating that either index or coordinates must be provided.

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?

No output schema, no annotations. For a click action in browser automation, more context about waiting, error handling, and page transition behavior would improve completeness. Description is functional but minimal.

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 description coverage is 100%, so baseline is 3. Description adds minor context by clarifying the two modes (index vs coordinates) but does not specify mutual exclusivity or required conditions.

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 the action (click), the resource (element), and the two methods (by index from neko_get_state or by coordinates). It distinguishes from sibling tools like neko_double_click or neko_hover.

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?

No explicit guidance on when to use this tool versus alternatives like neko_double_click or neko_hover. The description does not specify prerequisites or when not to use it.

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