Skip to main content
Glama
TacosyHorchata

Pilot

by TacosyHorchata
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

pilot_navigate

Navigate the browser to a URL and get confirmation with HTTP status, content preview, and interactive elements after the page loads.

Instructions

Navigate the browser to a URL and wait for DOM content to load. Use when the user wants to go to a specific webpage, URL, or link.

For read tasks ("go to X and tell me Y"), prefer pilot_get — it returns full readable content + interactive elements in one call, eliminating a follow-up snapshot call.

Parameters:

  • url: The URL to navigate to (e.g., "https://example.com" or relative paths)

Returns: Confirmation message with the HTTP status code, content preview, and interactive elements.

Errors:

  • "Invalid URL": The URL format is malformed. Provide a complete URL including the protocol.

  • Timeout (15s): The page took too long to load. Try pilot_navigate again or check the URL.

  • "Navigation denied": The URL was rejected by security validation (e.g., file:// on restricted origins).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to navigate to (e.g., "https://example.com")

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

No annotations provided, but description discloses wait for DOM content, return value (status code, preview, interactive elements), and errors with timeouts and security restrictions. Lacks detail on side effects like page history or cookies.

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?

Description is concise, front-loaded with purpose, and structured into clear sections (usage, parameters, returns, errors) with no wasted words.

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

Completeness5/5

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

Covers all necessary aspects for a navigation tool: purpose, alternative usage, parameter, return value, and common errors. No output schema, but return format is described adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with url parameter. Description adds value by mentioning relative paths and linking to error guidance, going beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states specific verb (navigate) and resource (browser to a URL), and differentiates from sibling pilot_get for read tasks.

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

Usage Guidelines5/5

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

Explicitly states when to use (going to a webpage) and when not to (prefer pilot_get for read tasks), with clear alternatives.

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