Skip to main content
Glama
Sign In
neko-browser

neko-browser

by aliksir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

neko_check

Set the checked state of a checkbox or radio button using its element index. Automates form input actions.

Instructions

Check or uncheck a checkbox or radio button element.

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_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYesElement index from neko_get_state
checkedNotrue=check, false=uncheck (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool changes the checked state, but does not mention any behavioral traits such as waiting, interaction requirements, or what happens if the element is already in the target state.

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 concise sentence with no extraneous information, front-loading the core purpose effectively.

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?

For a simple action tool with full schema coverage and no output schema, the description is nearly complete. It could be improved by noting radio button grouping behavior, but overall provides sufficient context.

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 coverage is 100% with both parameters described. The description adds minimal value beyond the schema, not providing additional semantic context for the parameters.

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 ('check or uncheck') and the target element type ('checkbox or radio button'), effectively differentiating from siblings like neko_click (generic click) and neko_fill (text input).

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?

The description implies usage for checkboxes and radio buttons, but lacks explicit guidance on when to use this tool over alternatives like neko_click, and does not mention prerequisites or context where it is not appropriate.

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