Skip to main content
Glama
MathiasPaulenko

WaveXisMCP

by MathiasPaulenko
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

wavexis_click

Destructive

Click a webpage element by CSS selector to trigger actions like form submission, control toggling, or page navigation. Returns status JSON.

Instructions

Click an element matching a CSS selector.

Use wavexis_double_click for double clicks, wavexis_right_click for context menus, or wavexis_nl_click when you only have a text description.

Side effects: Triggers a click event on the target element, which may submit forms, toggle controls, or navigate the page. Returns: JSON string with keys: 'status' ('ok'/'error'). On error also 'error', 'tool', 'type', 'message', 'suggestion' (all str).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changedv1.6.24
    • addedInput schema / $defs / ClickInput / properties / backend / description
      Added value: +"Backend: 'cdp', 'bidi', or 'auto'"
    • addedInput schema / $defs / ClickInput / properties / backend / enum
      Added value: +[
+  "cdp",
+  "bidi",
+  "auto"
+]
    • addedInput schema / $defs / ClickInput / properties / button / enum
      Added value: +[
+  "left",
+  "right",
+  "middle"
+]
    • addedInput schema / $defs / ClickInput / properties / click_count / description
      Added value: +"Number of clicks to perform"
    • addedInput schema / $defs / ClickInput / properties / headless / description
      Added value: +"Run browser in headless mode"
    • addedInput schema / $defs / ClickInput / properties / selector / minLength
      Added value: +1
    • addedInput schema / $defs / ClickInput / properties / session_id / description
      Added value: +"Active session ID. If omitted, a stateless session is created for this call."
    • addedInput schema / $defs / ClickInput / properties / url / description
      Added value: +"URL to navigate to (required without session_id)"
    • addedInput schema / $defs / ClickInput / properties / wait_timeout / description
      Added value: +"Timeout in ms for wait conditions"
    • addedInput schema / $defs / ClickInput / properties / wait_timeout / maximum
      Added value: +300000
    • addedInput schema / $defs / ClickInput / properties / wait_timeout / minimum
      Added value: +1000
  2. First observedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true and idempotentHint=false. The description adds specific side effects (triggers click, may submit forms, toggle controls, navigate page) and details the return format, providing useful context beyond the structured 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?

The description is extremely concise: three sentences covering purpose, alternatives, side effects, and return format. Every sentence earns its place, with no fluff. Front-loaded with the core action.

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 complexity and the presence of an output schema (not shown but indicated), the description adequately covers the core behavior, side effects, and return structure. It distinguishes itself among many siblings. Minor gap: no parameter constraints (e.g., selector must exist) beyond side effects.

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?

The description mentions 'CSS selector' but does not elaborate on other parameters like url, button, backend, or click_count. The schema itself provides descriptions for all parameters, so the description adds marginal value. Baseline score of 3 is appropriate given schema coverage.

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 opens with a clear verb-resource pair: 'Click an element matching a CSS selector.' It immediately distinguishes from siblings by naming alternative tools for double-click, right-click, and text-based clicking, making the purpose unambiguous.

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 explicitly states when to use alternative tools (wavexis_double_click, wavexis_right_click, wavexis_nl_click), providing clear context for selection. It lacks an explicit 'when not to use' but the alternatives cover the main exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MathiasPaulenko/wavexis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server