Skip to main content
Glama

open_tab

Opens a browser tab for a URL, launching the instance if needed, activating the tab, and waiting until the page loads.

Instructions

Opens a tab (launching the instance if needed; a fresh instance's untouched blank start tab is used, once, instead of opening a second one), makes it the active tab in front, and waits for 'url' to load. Returns {tab_id, target_id, url, label}; a network error fails naming the tab, which stays open.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL to load. Default: about:blank.
labelNoUnique label for the tab.
instance_idNoDefault: 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare destructiveHint=false, so the description carries most of the burden and does so well: it discloses the instance auto-launch, the one-time blank-tab reuse, the focus/activation side effect, the blocking wait for load, the exact return shape, and the failure semantics (network error names the tab, which stays open). This is precisely the context an agent needs to predict state after the call.

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?

Two sentences, front-loaded with the action and its side effects, followed by return/failure behavior; no filler. The nested parenthetical is slightly convoluted to parse but every clause carries real 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?

Completeness is strong for a 3-parameter tool with no output schema: the return object is named inline and error behavior is described. The only residual gap is guidance on choosing this tool over navigate/open_instance, which is a usage rather than a behavioral omission.

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?

With schema description coverage at 100%, the schema already documents url, label, and instance_id defaults. The description only reinforces that 'url' is awaited and that 'label' comes back in the return object, adding little beyond structured data, so the baseline of 3 applies.

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?

States a specific verb and resource ('opens a tab'), then enumerates the concrete side effects: launching the instance if needed, reusing a fresh instance's blank start tab once, activating it in front, and waiting for the URL to load. An agent can distinguish this from open_instance or switch_tab purely from the described behavior.

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?

There is useful routing information embedded in the parenthetical — an agent learns it does not need to call open_instance first, and that a blank start tab will be consumed rather than duplicated. But there is no explicit when-to-use vs when-not guidance (e.g., when to prefer navigate on an existing tab, or switch_tab instead), so the guidance is implied rather than stated.

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