WaveXisMCP

wavexis_new_tab

Open a new browser tab without leaving the current page, optionally navigating to a specified URL. Use this to load pages in parallel while keeping the active tab intact.

Instructions

Create a new browser tab, optionally navigating to a URL.

Use to open a parallel page without losing the current tab; use wavexis_navigate to change the current tab's URL instead.

Side effects: Opens a new browser tab; if a URL is provided, issues a network request to it. Returns: JSON string with keys: 'status' ('ok'/'error'), 'tab_id' (str), 'url' (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_new_tab"
  }
}

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 / NewTabInput / properties / session_id / description
```
Added value: +"Active session ID from wavexis_session_open"
```
- addedInput schema / $defs / NewTabInput / properties / url / description
```
Added value: +"URL for the new tab"
```
First observedv1.0.1Jul 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Disclosed side effects: opens a new tab and optionally issues a network request. This aligns with annotations (readOnlyHint=false, openWorldHint=true). No contradictions. Could elaborate on whether the URL must be valid or if any tab limits apply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with purpose and usage distinction. It includes side effects and return format in separate sentences. Slight improvement could be grouping related info, but overall efficient.

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?

For a simple tab-creation tool, the description covers purpose, usage, side effects, and return. It doesn't mention limitations or prerequisites beyond what the schema provides, but given the presence of output schema and annotations, it is sufficiently complete.

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 description coverage is low (0%). The description only mentions 'URL' indirectly; it does not explain 'session_id' or that the URL defaults to 'about:blank'. The schema itself provides descriptions, but the tool description adds little 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 clearly states the action ('Create a new browser tab') and the optional parameter 'URL'. It distinguishes itself from the sibling tool 'wavexis_navigate' by explaining when to use each.

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?

Explicitly tells when to use (open parallel page) and when not to (use wavexis_navigate for current tab). It doesn't mention prerequisites like an active session, but the schema indicates 'session_id' is required and its source.

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

Deploy Server