WaveXisMCP

wavexis_close_tab

DestructiveIdempotent

Close a browser tab by ID to remove it from the active session and free its resources. Use this when a tab is no longer needed; unsaved data in that tab is lost.

Instructions

Close a browser tab by its ID.

Use to clean up tabs created with wavexis_new_tab; use wavexis_session_close to terminate the entire session instead.

Side effects: Closes the specified tab and discards its page state. Destructive — unsaved data in that tab is lost. 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_close_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 / CloseTabInput / properties / session_id / description
```
Added value: +"Active session ID from wavexis_session_open"
```
- addedInput schema / $defs / CloseTabInput / properties / tab_id / description
```
Added value: +"Tab ID to operate on"
```
First observedv1.0.1Jul 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description adds context beyond annotations: it states side effects ('Closes the specified tab and discards its page state') and notes data loss ('unsaved data in that tab is lost'). While annotations already indicate destructiveHint=true, the description enriches this with specific implications, though it omits details like authentication requirements or rate limits.

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 and well-structured: it starts with the main action, follows with usage context, side effects, and return format, all in a few sentences without redundancy.

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 close action, the description covers enough: it mentions the return format, side effects, and relationship to sibling tools. However, it could note that the tab ID comes from wavexis_list_tabs or similar, but the schema hints at the source. Overall sufficient given the tool's simplicity.

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?

Even though the context indicates 0% schema description coverage, the input schema actually provides clear descriptions for both parameters (tab_id and session_id). The tool description adds no further parameter meaning, so baseline 3 applies as the schema already does the job.

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 and resource: 'Close a browser tab by its ID.' It distinguishes from the sibling tool wavexis_session_close by noting that the latter terminates the entire session, making the purpose specific and unambiguous.

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?

The description explicitly advises when to use this tool ('clean up tabs created with wavexis_new_tab') and provides an alternative tool ('use wavexis_session_close to terminate the entire session instead'), offering clear guidance on usage context.

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

Deploy Server