WaveXisMCP

wavexis_activate_tab

Idempotent

Bring a browser tab to the foreground using its ID to switch the active tab. This ensures subsequent navigation and interaction tools act on that tab.

Instructions

Focus (bring to front) a browser tab by its ID.

Use to switch the active tab before running navigation or interaction tools; use wavexis_list_tabs to obtain tab IDs first.

Side effects: Changes the browser's active tab; subsequent tool calls operate on the newly focused tab. 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_activate_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 / ActivateTabInput / properties / session_id / description
```
Added value: +"Active session ID from wavexis_session_open"
```
- addedInput schema / $defs / ActivateTabInput / properties / tab_id / description
```
Added value: +"Tab ID to operate on"
```
First observedv1.0.1Jul 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds valuable context: side effect of changing active tab and that subsequent calls operate on the new tab, plus return format. No contradiction with 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?

Description is short, well-structured, and front-loaded. Each sentence serves a clear purpose: purpose, usage hint, side effects, and return value. No redundant information.

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?

Covers purpose, prerequisites, side effects, and return format. Though it doesn't explicitly reiterate the required session_id from schema, the overall information is sufficient for correct usage with the input schema present.

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 already provides descriptions for both parameters ('Tab ID to operate on', 'Active session ID from wavexis_session_open'). The tool description does not add further parameter semantics, making it adequate but not enhanced.

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?

Description clearly states 'Focus (bring to front) a browser tab by its ID', specifying the verb and resource. It distinguishes from sibling tools like wavexis_list_tabs (listing) and wavexis_new_tab (creating) by focusing on activation.

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 says to use before navigation/interaction tools and to obtain tab IDs via wavexis_list_tabs first. This provides clear context and a prerequisite, though no explicit when-not-to-use advice is given.

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

Deploy Server