Skip to main content
Glama

switch_tab

Make a browser tab the target for commands that omit tab_id, and bring it to the foreground unless activate is false.

Instructions

Makes a tab the target of the tools that omit tab_id, and brings it to the foreground unless 'activate' is false.

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": {
      "tab_id": "<tab_id>"
    },
    "name": "switch_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYesThe Tab ID to switch to (e.g. 'tab-1').
activateNoBring it to the foreground. Default: true.
instance_idNoDefault: 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A3.6/5.0
Behavior3/5

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

Beyond the single destructiveHint=false annotation, the description usefully discloses a non-obvious side effect: it changes the implicit target of other tools that omit tab_id, and it moves the tab to the foreground by default. It does not cover failure modes (invalid tab_id), cross-instance behavior, or whether foregrounding is undone by other actions.

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?

A single compact sentence with the primary effect front-loaded and the activate caveat trailing. Nothing is redundant or padded.

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 three-parameter tool with no output schema, the description covers the essential behavior and default. Only minor gaps remain around error conditions and instance scoping, which the schema partially implies.

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?

Schema coverage is 100% and each parameter already carries a description, so the schema does the heavy lifting. The description echoes the activate default rather than adding new semantics for it, though the 'target of tools that omit tab_id' framing does clarify why tab_id matters.

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?

States a specific action on a specific resource (making a tab the active target) and describes the follow-on effect on other tools, which distinguishes it from list_tabs/close_tab/open_tab. It never names a sibling or explicitly says when to pick one of those instead, so the differentiation is implied rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'the tools that omit tab_id' – an agent can infer this is a prerequisite step before tab-scoped actions. There is no explicit when-to-use/when-not-to-use guidance, no mention of open_tab for creating tabs, and no statement about what happens if the tab is in a different instance.

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