Skip to main content
Glama
Sign In
chrome-fast

chrome-fast

by ventos312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

navigate

Opens a URL in the current tab and returns page content as an accessibility tree with numbered element references for click and type actions.

Instructions

Navigate the current tab to a URL and return the page content as an accessibility tree with numbered element refs you can pass to click/type.

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
urlYesURL to open. A bare host such as example.com is treated as https://example.com.
timeoutNoMaximum time to wait for the page, in ms (default: 30000). On timeout the content so far is returned with a note.
waitUntilNoWhen navigation counts as done (default: load). networkidle also waits until the network has been quiet for 500 ms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that navigation targets the current tab and returns an accessibility tree with numbered refs, which adds value beyond the schema. It does not cover error behavior, redirects, or what happens to tab state on failure.

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 followed by the return format and ref usage. No filler or unnecessary wording.

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?

For a navigation tool with a fully described input schema and no output schema, the description covers purpose, scope (current tab), return format, and ref usage. It leaves out failure and error semantics, which keeps it from a 5, but is otherwise sufficient.

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%, so the schema already documents url, timeout, and waitUntil in detail. The description adds no parameter-specific meaning beyond restating that a URL is navigated to; baseline 3 is appropriate.

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 ('current tab to a URL'), and describes the return value as an accessibility tree with numbered element refs. It does not explicitly distinguish from sibling get_page, so it falls 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 Guidelines3/5

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

Implies use when you need to load a URL and obtain interactive refs for click/type, but never states when to use this instead of get_page or tab_new, nor any prerequisites or exclusions. The context is clear enough to infer the main use case, but explicit alternatives are absent.

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