Skip to main content
Glama
Sign In
duplex

duplex

by Eric-huang799
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

new_tab

Open a new tab in the browser, optionally navigating to a URL. The new tab becomes the visible tab unless the user is actively using the current page.

Instructions

Open a new tab in the browser, optionally navigating to a URL. The new tab becomes the visible tab unless the user is actively using the current page.

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

Input Schema

NameRequiredDescriptionDefault
urlNoURL to open; omit for a blank page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the burden, and it does add one non-obvious behavioral trait: the new tab becomes the visible tab unless the user is actively using the current page. However, it doesn't disclose what happens on failure, permissions, or whether the tab returns a handle/id, which matters for follow-up calls.

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, zero waste, with the core action front-loaded. Slightly compaction could merge the visibility caveat, but it is efficiently sized.

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 simple one-param tool this is largely adequate, but with no annotations and no output schema, one might expect the description to state what the call returns (e.g., a tab identifier usable with switch_tab) since that is otherwise undocumented.

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% with a single optional parameter already documented ('URL to open; omit for a blank page'). The description merely restates the URL option, adding no syntax or format detail beyond the schema. 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?

States a specific verb+resource: open a new tab, with optional URL. Clear enough to distinguish from switch_tab and close_tab by name alone, though it doesn't explicitly name those siblings.

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?

Implied usage only: 'optionally navigating to a URL' and the visibility note give context for when to call, but there is no explicit when/when-not guidance versus switch_tab or navigate.

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