Skip to main content
Glama
Sign In
chrome-fast

chrome-fast

by ventos312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tab_new

Opens a new browser tab, attaches to it, and optionally navigates to a URL. Returns the page content for automation.

Instructions

Open a new tab, attach to it and optionally navigate it to a URL. Returns the page content.

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_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL to open (default: a blank tab)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/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; it discloses the key side effect (a new tab is created and the session attaches to it) and that page content is returned. It omits whether the previously attached tab is detached, whether focus changes, limits on tab count, and failure behavior for invalid URLs.

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 short sentences, front-loaded with the primary action and finishing with the return value. No filler, though the return-value sentence is minimally informative given there is no output schema.

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?

A simple one-optional-parameter tool with full schema coverage and no output schema; the description covers the action, the attach behavior, and the return value. Missing only edge-case behavior such as what happens if the URL is invalid or the tab limit is reached.

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 coverage is 100% and the single optional url parameter is already documented with its blank-tab default. The description restates the optionality but adds no format, scheme, or validation detail beyond the schema.

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 new tab, attach to it") plus an optional navigation step, which distinguishes it from tab_switch, tab_close, and navigate without naming them. Slightly short of a 5 because sibling differentiation is only implicit.

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 only implied: creating a tab is self-evident, and "optionally navigate it to a URL" hints at a relationship with the separate navigate and tabs tools but never states when to use one over the other. No exclusions or prerequisites are given.

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