Skip to main content
Glama

open_tab

Open a URL in a new browser tab that is shared with the agent, so it can read, click, and fill forms on that page alongside you.

Instructions

Open a URL in a new tab in the user's browser. The new tab is shared with you.

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": {
      "url": "<url>"
    },
    "name": "open_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
openerNoShared tab to open next to.
browserNoBrowser key from list_tabs when several browsers are connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 disclosure burden. It does add one genuinely useful behavioral fact beyond the schema—'The new tab is shared with you,' meaning the agent can subsequently act on it—but says nothing about session prerequisites, failure modes when no browser is connected, or permitted URL schemes.

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 with zero waste, front-loading the action and following with the one behavioral fact worth knowing. Nothing is padded or repeated.

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

Completeness3/5

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

For a 3-parameter, non-destructive tool with no annotations and no output schema, the core action and the shared-tab consequence are covered. However, the relationship to 'list_tabs' (referenced by the 'browser' parameter) and prerequisites for opening a tab are left to the schema alone.

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 description coverage is 67%: 'opener' and 'browser' are self-documented, while 'url' is undocumented but obvious from the name. The description adds no meaning beyond the schema and never mentions 'opener' or 'browser', so the baseline 3 for high coverage applies.

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 verb and resource: 'Open a URL in a new tab in the user's browser.' An agent can tell it produces a new tab rather than mutating an existing one. It does not name or distinguish itself from the obvious sibling 'navigate', so it falls 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 explicit when-to-use guidance, no indication of when to prefer this over 'navigate', and no mention that a browser session must be active. Usage is only loosely implied by the verb, leaving the agent to infer the alternative.

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