PhantomHand

by SilenceEchoLab

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

browser_tab_switch

Switch to a specific browser tab using its tab ID, obtained from the tab list.

Instructions

Switch to a specific browser tab by its tab ID (obtained from browser_tab_list).

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": {
      "tabId": "<tabId>"
    },
    "name": "browser_tab_switch"
  }
}

Input Schema

Name	Required	Description	Default
`tabId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jul 5, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description must fully cover behavioral traits. It describes the action as a switch but does not disclose side effects (e.g., focusing the tab, potential page load). For a simple action, this is adequate but lacks depth.

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 a single, front-loaded sentence with no unnecessary words. Every element serves a purpose.

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 tool with one required parameter and no output schema, the description covers the essential information: what it does and how to get the parameter. It does not mention error handling or invalid IDs, but the simplicity makes this acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates by explaining the parameter's origin: 'by its tab ID (obtained from browser_tab_list)'. This adds meaningful context beyond the raw 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 uses a specific verb 'Switch' and resource 'browser tab', and clearly states how to obtain the tab ID from browser_tab_list, distinguishing it from sibling tools like browser_tab_close, browser_tab_new, and browser_tab_list.

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 implies that the tab ID should come from browser_tab_list, providing clear context for usage. However, it does not explicitly state when not to use this tool or mention alternatives.

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