Skip to main content
Glama

tab_open

Opens a URL in a new agent tab within the agent’s own browser window and waits for the page to load, keeping agent activity separate from the user’s tabs.

Instructions

Open a URL in a new agent tab (in the agent's own window) and wait for it to load.

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": "tab_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.4

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful behavior: a new tab is created, it is isolated to the agent's own window, and the call is synchronous in that it waits for load. It says nothing about what happens on navigation failure, timeouts, blocked popups, or whether the new tab gains focus.

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?

One sentence, front-loaded with the action and scoped by the parenthetical, with the wait-for-load behavior appended. No filler or redundancy.

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 one-parameter tool this is close to adequate, and the synchronous-load detail is important for sequencing follow-up calls. However, with no output schema, the description never indicates what the call returns (tab handle, final URL, or nothing), which an agent needs to chain into click/page_text/tab_close.

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 description coverage is 0% for the single required `url` parameter, so the description should compensate but only offers 'a URL'. It gives no scheme requirements, no note on relative URLs or redirects, and no example, leaving the parameter's accepted format undetermined.

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 agent tab') and adds scope qualifiers ('in the agent's own window') plus the blocking behavior ('wait for it to load'). It does not explicitly name the closest sibling (navigate) and say how it differs, so an agent must infer that navigate reuses an existing tab.

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 'new agent tab / agent's own window' framing — you use it when you need an isolated tab — but there is no explicit when-to-use versus when-to-use-navigate guidance or any stated prerequisite such as an existing browser session.

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