WaveXisMCP

wavexis_uncheck

DestructiveIdempotent

Uncheck a checkbox by clicking its CSS selector, firing change events to update form state.

Instructions

Uncheck a checkbox matching a CSS selector by clicking it.

Use wavexis_check to check a checkbox or wavexis_click for generic element activation.

Side effects: Clicks the target checkbox to toggle it to unchecked, firing change events. Returns: JSON string with keys: 'status' ('ok'/'error'). On error also 'error', 'tool', 'type', 'message', 'suggestion' (all str).

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": {
      "input": "<input>"
    },
    "name": "wavexis_uncheck"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.6.24Jul 29, 2026
- addedInput schema / $defs / CheckInput / properties / selector / minLength
```
Added value: +1
```
- addedInput schema / $defs / CheckInput / properties / session_id / description
```
Added value: +"Active session ID from wavexis_session_open"
```
First observedv1.0.1Jul 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Description adds side effects ('Clicks the target checkbox to toggle it to unchecked, firing change events') beyond annotations, and does not contradict the destructiveHint or idempotentHint 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?

Three sentences with clear front-loading: purpose, usage guidelines, then side effects and return value. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage, side effects, return format, and distinguishes from siblings. The output schema exists, but the description still provides helpful details. Complete for the tool's complexity.

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 descriptions cover 0% of parameters, but the tool description does not mention parameters or add meaning beyond the schema's own parameter descriptions. No additional value is provided.

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?

Clearly states 'Uncheck a checkbox matching a CSS selector by clicking it.' Verb and resource are specific, and the description distinguishes this from sibling tools like wavexis_check and wavexis_click.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to use wavexis_check for checking and wavexis_click for generic clicks, providing clear when-to-use and when-not-to-use guidance.

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

Deploy Server