Skip to main content
Glama
Sign In
omni-browser

omni-browser

by rianprei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_switch_tab

Switch the active Chromium browser tab by index to focus a specific tab for navigation, reading, or interaction.

Instructions

Switch active browser tab.

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": {
      "index": "<index>"
    },
    "name": "browser_switch_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses almost nothing: no note on failure when the index is out of range, whether the switch brings the browser window to the foreground, or whether background tabs are affected. 'Switch' implies a state change on the browser session, but the consequences are unstated.

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?

One short, front-loaded sentence with no filler. Its brevity is appropriate in form, though it comes at the cost of the substance missing elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no annotations and no output schema, the definition should at minimum pin down what the index means and what happens on an invalid value. As written, an agent must guess the indexing convention before it can call the tool correctly.

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 coverage is 0% for the single required parameter, so the description must compensate and does not. Whether 'index' is 0-based or 1-based, and whether it refers to the ordering returned by browser_tabs, is left entirely ambiguous — a critical gap for a tool whose only input is that index.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Switch active browser tab'), so an agent immediately knows the operation. It does not distinguish itself from the sibling browser_tabs (likely for listing tabs) or explain the relationship between them, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this instead of browser_tabs or browser_open, and no prerequisite such as discovering the tab index first. The agent must infer the entire workflow from sibling names.

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

Deploy Server

Other Tools