Skip to main content
Glama
Sign In
chrome-fast

chrome-fast

by ventos312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tab_switch

Switches to a specified Chrome tab by target ID, brings it to the front, and returns its page content so agents can continue work in that tab.

Instructions

Attach to another tab by its target ID (from the tabs tool) and bring it to the front. Returns its page content.

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": {
      "targetId": "<targetId>"
    },
    "name": "tab_switch"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetIdYesTarget ID of the tab to switch to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two useful behaviors: a UI side effect ('bring it to the front') and the return value ('Returns its page content'). It says nothing about failure modes (invalid or stale targetId), whether the previously active tab loses its attachment, or any permission constraints, which matters for a state-changing browser tool.

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?

Two short sentences, no redundancy; the action and the ID provenance are front-loaded, with the return value trailing. Every clause carries 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?

For a one-parameter tool with no output schema, the description covers the action, the required input source, the side effect, and the returned content. Only error/edge-case behavior is absent, which is minor at this complexity.

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?

With a single parameter and 100% schema coverage, the baseline is 3, but the description adds real meaning by stating where the targetId must come from (the tabs tool) — provenance the schema's 'Target ID of the tab to switch to' does not convey. It does not describe the ID format or whether IDs persist across sessions.

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 pairs a specific verb ('Attach to... and bring it to the front') with a specific resource ('another tab'), and clarifies that 'switch' means two concrete actions. Pointing to 'the tabs tool' as the source of the ID implicitly separates it from tab_new and tab_close, though it never names those siblings as distinct alternatives.

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 rather than stated: the agent can infer this is for moving control to an already-open tab, and that it must first obtain an ID from the tabs tool. There is no explicit when-to-use, when-not-to-use, or alternative (e.g., tab_new for a fresh tab), leaving the agent to reconstruct the workflow.

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