Skip to main content
Glama
Sign In
duplex

duplex

by Eric-huang799
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

navigate

Open a URL in a browser tab, defaulting to the active tab, so an MCP client can change the page in the shared human-AI browser session.

Instructions

Navigate a tab (default: active tab) to a URL.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute URL, e.g. https://example.com
tabIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but discloses little. It does not say whether navigation waits for page load, what happens to the existing page state, whether it requires permissions, or whether it is reversible — all material for an operation that replaces a tab's content.

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?

A single efficient sentence, front-loaded with the verb and target. Every word earns its place, with no padding or redundancy.

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

Completeness2/5

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

For a navigation tool with no annotations and no output schema, the description is thin. It omits load/wait semantics, error behavior on invalid URLs, and how it relates to sibling navigation/opening tools, leaving the agent under-informed for correct invocation.

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 50%: url is documented with an example, but tabId has no schema description. The description compensates by clarifying that omitting tabId targets the active tab, adding real meaning to tabId, though it offers no format or range detail for the numeric id.

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 ('navigate') and resource ('a tab ... to a URL'), plus the default target ('default: active tab'). It is a clear purpose, though it does not explicitly distinguish itself from siblings like new_tab or switch_tab, leaving that to inference.

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?

The parenthetical '(default: active tab)' implies you can target a specific tab via tabId, giving some contextual clue. However, it never states when to use navigate versus new_tab, switch_tab, or opening a fresh tab, so guidance is only implied.

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