Skip to main content
Glama
Sign In
Antigravity Browser Operator

Antigravity Browser Operator

by hashan-lakshitha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_navigate

Navigates a specified or active Chrome tab to a URL and waits for the page to load, so agents can control browsing within existing sessions.

Instructions

Navigates the specified or active tab in the user’s Chrome browser to a URL and waits for page load.

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to navigate to.
tabIdNoOptional tab ID. If omitted, navigates the active tab.
waitUntilNoWait condition: "interactive" (default, fast - resolves as soon as DOM is ready) or "complete" (waits for all background ads/trackers).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.0
    • addedInput schema / properties / waitUntil
      Added value: +{
+  "description": "Wait condition: \"interactive\" (default, fast - resolves as soon as DOM is ready) or \"complete\" (waits for all background ads/trackers).",
+  "enum": [
+    "interactive",
+    "complete"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.1

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 full burden, and it does disclose one real behavioral trait: the call blocks until page load completes. It says nothing about what happens on navigation failure (bad URL, timeout, blocked page), whether an error is thrown or returned, or whether any auth/profile state is required.

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?

A single front-loaded sentence with the verb, scope, and blocking behavior in one pass; no filler, no restatement of the name, nothing that could be cut without losing information.

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 simple three-parameter navigation tool with no output schema, the description covers what the tool does and that it waits for load. The remaining gap is failure semantics — what an agent should expect when navigation does not succeed — which is material for an agent that must recover from errors.

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 three parameters — including the waitUntil enum semantics — are already fully documented in the schema. The description's 'specified or active tab' only restates the tabId default behavior, adding no new meaning beyond structured fields.

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 (navigates) and resource (tab in the user's Chrome browser) plus the target (a URL), which is unambiguous. It does not name the sibling it is not — notably browser_new_tab, which is the obvious confusion point — so 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?

The phrase 'specified or active tab' implies this tool drives an existing tab rather than opening one, which hints at when to use it versus browser_new_tab. However, there is no explicit when-to-use/when-not guidance, no mention of prerequisites such as a launched profile, and no named alternative.

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