WaveXisMCP

wavexis_iframe_fill

Destructive

Fill an input element inside an iframe with a value using session ID and CSS selectors. Triggers input/change events to enable automated form interaction in embedded web content.

Instructions

Fill an input element inside an iframe with a value.

Use wavexis_iframe_click to submit or activate the field after filling.

Side effects: Mutates the input value within the iframe; may trigger input/change events. Returns: JSON string with keys: 'status' ('ok'/'error').

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_iframe_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.

Changed3 schema fields changedv1.6.24Jul 29, 2026
- addedInput schema / $defs / IframeFillInput / properties / iframe_selector / minLength
```
Added value: +1
```
- addedInput schema / $defs / IframeFillInput / properties / selector / minLength
```
Added value: +1
```
- addedInput schema / $defs / IframeFillInput / properties / session_id / description
```
Added value: +"Active session ID from wavexis_session_open"
```
Addedv1.2.0Jul 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description details side effects: 'Mutates the input value within the iframe; may trigger input/change events.' This adds specific behavioral context beyond the annotations (destructiveHint=true) and clarifies that the tool can trigger events, aiding in agent decision-making.

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 concise with four sentences covering purpose, usage guidance, side effects, and return format. Each sentence serves a distinct purpose and is front-loaded with the primary action, making it efficient and easy to parse.

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 four parameters and existing annotations, the description covers the key behavioral aspects (purpose, side effects, return format, and guidance). It could be improved by mentioning prerequisites like an active session or error conditions, but overall it sufficiently equips an agent to understand the tool's 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?

The input schema already provides clear descriptions for all nested parameters (session_id, iframe_selector, selector, value). The tool description does not add extra parameter information, and the top-level 'input' parameter lacks a description. However, the schema coverage is effectively high for the nested fields, so the description adds minimal value beyond the schema.

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 states 'Fill an input element inside an iframe with a value,' using a specific verb (fill) and resource (iframe input element). It clearly differentiates from sibling tools like wavexis_fill (main page) and wavexis_iframe_click (clicking), making the tool's 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 advises 'Use wavexis_iframe_click to submit or activate the field after filling,' providing explicit context on when to use this tool and a follow-up action. It implies not to use this tool for clicking or submission, though it lacks explicit 'when not to use' statements.

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

Deploy Server