WaveXisMCP

wavexis_console_clear

DestructiveIdempotent

Clears buffered console messages before capturing fresh logs, avoiding stale entries. Resets the session's in-memory console buffer.

Instructions

Clear all buffered console messages for the session.

This tool mirrors Playwright's API for compatibility; use it before capturing a fresh set of console logs to avoid stale entries.

Side effects: Resets the session's in-memory console message buffer. 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_console_clear"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.6.25Aug 21, 2026
- addedInput schema / $defs / ConsoleClearInput / properties / session_id / description
```
Added value: +"Active session ID from wavexis_session_open"
```
Addedv1.6.24Jul 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description explicitly discloses the wholesale buffer reset ('Resets the session's in-memory console message buffer') and the exact return format ('JSON string with keys: status ('ok'/'error')'). This complements the annotations by clarifying what the destructive hint means in practice and what the caller will receive. No contradiction with the annotations exists.

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 four precise sentences, each with a distinct role: operation, usage placement, side-effect disclosure, and return value. It is front-loaded with the action and contains no filler or redundant phrasing.

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?

For a single-parameter utility with helpful annotations and a schema description for the parameter, the description fully covers the intended effect, the recommended timing, the session-scoped nature, and the expected response shape. An agent has everything needed to invoke it correctly and understand its impact.

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 sole parameter, session_id, is already described in the schema as 'Active session ID from wavexis_session_open.' The tool's text does not mention the parameter, but the schema provides sufficient meaning and provenance. Given schema coverage exists, the description need not repeat it.

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 uses a specific verb and resource: 'Clear all buffered console messages for the session.' It clearly defines the operation's scope and distinguishes it from cookie- or tab-related tools in the sibling list. There is no ambiguity about what the tool does.

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 provides a direct usage trigger: 'use it before capturing a fresh set of console logs to avoid stale entries.' This gives the agent a concrete scenario for when to call the tool without requiring inference. It does not explicitly name alternatives or exclusions, but none are needed for this focused utility.

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

Deploy Server