Skip to main content
Glama

pilot_navigate

Navigate to web URLs to retrieve HTTP status codes and final destination addresses for automated browsing tasks.

Instructions

Navigate to a URL. Returns HTTP status code and final URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to navigate to

Implementation Reference

  • The implementation of the pilot_navigate tool handler.
    server.tool(
      'pilot_navigate',
      'Navigate to a URL. Returns HTTP status code and final URL.',
      { url: z.string().describe('URL to navigate to') },
      async ({ url }) => {
        await bm.ensureBrowser();
        try {
          await validateNavigationUrl(url);
          const page = bm.getPage();
          const response = await page.goto(url, { waitUntil: 'domcontentloaded', timeout: 15000 });
          const status = response?.status() || 'unknown';
          bm.resetFailures();
          return { content: [{ type: 'text' as const, text: `Navigated to ${url} (${status})` }] };
        } catch (err) {
          bm.incrementFailures();
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It compensates for the missing output schema by documenting return values ('HTTP status code and final URL'), which implies redirect following. However, it omits critical execution details like whether it waits for page load, timeout behavior, or error handling on 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description consists of two efficient sentences with no redundancy. It front-loads the action and efficiently appends the return value information, with every word earning its place.

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 single-parameter navigation tool, the description covers the basic action and return values. However, given the browser automation context with 40+ sibling tools, it lacks completeness by not mentioning that this changes the active page context for subsequent tool calls or how it handles network 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%, meaning the 'url' parameter is fully documented in the schema ('URL to navigate to'). The description does not add additional semantic context about the parameter format or constraints, warranting the baseline score of 3.

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?

The description clearly states the action ('Navigate') and target ('URL'), distinguishing it from sibling interaction tools like pilot_click or pilot_back. However, it does not explicitly differentiate from pilot_reload or clarify that this loads a new page versus modifying the current one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives (e.g., pilot_back for history, pilot_click for link navigation) or prerequisites (like needing a valid URL format). It merely states what the tool does.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TacosyHorchata/Pilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server