Skip to main content
Glama

tab_create

Open a new browser tab, optionally at a URL, and wait for it to load; the tab shares the current page’s container and logins so you can work without reusing the user’s tabs.

Instructions

Open a new tab in Zen, optionally at a URL, and wait for it to load. It opens in the same container as the page the user is on, so it shares the same logins. Prefer working in a tab you created over reusing one of the user's tabs.

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

Input Schema

NameRequiredDescriptionDefault
urlNoURL to open; blank tab if omitted
plainNoOpen outside any container. By default the tab uses the same container (set of logins) as the page the user is on.
activeNoBring the tab to the front (default true)
windowIdNoWindow to open it in (default: the window in front)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that the call blocks until load completes, and that the tab inherits the current page's container so it shares logins. That container/logins detail is non-obvious and not in the schema. It omits whether a tab handle/id is returned (there is no output schema) and whether the wait can fail or time out, which are meaningful gaps for a caller who needs the new tab's identity.

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, front-loaded with the action and its load-wait behavior, followed by the container caveat and the usage preference. Every clause adds information; nothing is redundant with the schema.

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 side-effecting UI tool with zero annotations and no output schema, the definition covers container/logins and load-wait, which are the main surprises. It still leaves the caller unsure what the call returns (a tab reference to pass to click/read_page) or how failures manifest, which matters given the sibling tools all operate on tab handles.

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 100%, so all four parameters (url, plain, active, windowId) are already documented in the schema, including the container semantics of `plain`. The description only restates that the URL is optional and the container default, adding no syntax, ordering, or interaction detail beyond structured data. Baseline 3 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?

The description states a concrete verb and resource ("Open a new tab in Zen") plus the optional URL and the load-wait step, so an agent knows exactly what the call does. It implicitly separates this from reusing an existing tab (navigate/click on a user tab) but never names a sibling tool, keeping it just 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 Guidelines4/5

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

"Prefer working in a tab you created over reusing one of the user's tabs" gives a clear default operating preference for when to call this rather than acting in the user's current tab. It stops short of explicit exclusions (e.g., when to call tab_close or navigate instead) or prerequisites, so it is clear context without full routing guidance.

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