WaveXisMCP

wavexis_fill

Destructive

Replace the current value of any input or textarea with a new string. Clears existing content, sets the provided value, and triggers a single input event for form automation.

Instructions

Fill an input element with a value, replacing existing content.

Use wavexis_type for character-by-character typing with key events, or wavexis_fill_form when filling multiple fields in one call.

Side effects: Clears the target input/textarea and sets its value to the provided string, firing a single input event. 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_fill"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv1.6.24Jul 29, 2026
- addedInput schema / $defs / FillInput / properties / backend / description
```
Added value: +"Backend: 'cdp', 'bidi', or 'auto'"
```
- addedInput schema / $defs / FillInput / properties / backend / enum
```
Added value: +[
+  "cdp",
+  "bidi",
+  "auto"
+]
```
- addedInput schema / $defs / FillInput / properties / headless / description
```
Added value: +"Run browser in headless mode"
```
- addedInput schema / $defs / FillInput / properties / selector / description
```
Added value: +"CSS selector for the target element"
```
- addedInput schema / $defs / FillInput / properties / selector / minLength
```
Added value: +1
```
- addedInput schema / $defs / FillInput / properties / session_id / description
```
Added value: +"Active session ID. If omitted, a stateless session is created for this call."
```
- addedInput schema / $defs / FillInput / properties / url / description
```
Added value: +"URL to navigate to (required without session_id)"
```
- addedInput schema / $defs / FillInput / properties / wait_timeout / description
```
Added value: +"Timeout in ms for wait conditions"
```
- addedInput schema / $defs / FillInput / properties / wait_timeout / maximum
```
Added value: +300000
```
- addedInput schema / $defs / FillInput / properties / wait_timeout / minimum
```
Added value: +1000
```
First observedv1.0.1Jul 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations indicate destructiveHint=true; description adds specific side effects: clears target, sets value, fires single input event. Also documents return format with status and error details. No contradictions.

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?

Concise, well-structured: purpose first, then usage guidelines, side effects, and return format. Every sentence adds value without redundancy.

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?

Given sibling tools, annotations, and schema descriptions, the description fully covers behavior, side effects, and return format. Output schema exists but description still documents return format explicitly.

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?

Input schema includes detailed descriptions for all parameters (e.g., selector, value). Description does not add additional parameter info but maintains baseline. Context signal indicates schema description coverage 0% but schema clearly has descriptions; if coverage were actually 0%, would need to compensate.

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 'Fill an input element with a value, replacing existing content.' Explicitly contrasts with sibling tools wavexis_type and wavexis_fill_form, specifying unique verb-resource-action.

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?

Provides explicit guidance: 'Use wavexis_type for character-by-character typing with key events, or wavexis_fill_form when filling multiple fields in one call.' This clearly differentiates usage scenarios.

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

Deploy Server