Skip to main content
Glama

navigate

Directs a web browser to a specified URL, enabling automated web navigation and interaction for data retrieval and task execution.

Instructions

Navigate to a specified URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to navigate to

Implementation Reference

  • The core handler function implementing the 'navigate' tool logic: validates URL, adds https:// if needed, calls page.goto(url), and returns success message.
    async function handleNavigate(page: Page, args: any): Promise<CallToolResult> {
      let { url } = args;
      if (!url) {
        return {
          isError: true,
          content: [
            { type: "text", text: "URL parameter is required for navigation" },
          ],
        };
      }
      if (!url.startsWith("http://") && !url.startsWith("https://")) {
        url = "https://" + url;
      }
      await page.goto(url);
      return {
        isError: false,
        content: [{ type: "text", text: `Navigated to ${url}` }],
      };
    }
  • Input schema for the 'navigate' tool, requiring a 'url' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        url: { type: "string", description: "The URL to navigate to" },
      },
      required: ["url"],
    },
  • src/index.ts:456-466 (registration)
    Registration of the 'navigate' tool in the TOOLS array, including name, description, and input schema.
    {
      name: "navigate",
      description: "Navigate to a specified URL",
      inputSchema: {
        type: "object",
        properties: {
          url: { type: "string", description: "The URL to navigate to" },
        },
        required: ["url"],
      },
    },
  • src/index.ts:916-917 (registration)
    Switch case in the main tool dispatcher (handleToolCall) that invokes the navigate handler.
    case "navigate":
      result = await handleNavigate(page, args);
  • src/index.ts:1068-1071 (registration)
    MCP server request handler for listing tools, exposing the 'navigate' tool via the TOOLS array.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('navigate') but doesn't describe what happens: whether it opens a new tab, reloads a page, handles errors, requires authentication, or has side effects like waiting for page load. For a tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

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 is a single, efficient sentence with zero waste: 'Navigate to a specified URL'. It is front-loaded and appropriately sized for a simple tool, making it easy to parse without unnecessary elaboration.

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?

Given the lack of annotations and output schema, the description is incomplete for a navigation tool. It doesn't explain what 'navigate' entails operationally (e.g., browser behavior, success/failure states) or what the tool returns (e.g., page title, status). For a tool with no structured data to compensate, this leaves significant gaps in understanding its use and outcomes.

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?

The schema description coverage is 100%, with the single parameter 'url' fully documented in the schema as 'The URL to navigate to'. The description adds no additional meaning beyond this, such as URL format requirements or validation rules. Given the high schema coverage, a baseline score of 3 is appropriate as the schema does the heavy lifting.

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 'Navigate to a specified URL' clearly states the action (navigate) and resource (URL), making the purpose immediately understandable. It distinguishes from siblings like 'click' or 'type' by focusing on URL navigation rather than page interaction. However, it doesn't specify what 'navigate' entails (e.g., loading a webpage in a browser), which prevents a perfect score.

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. It doesn't mention prerequisites (e.g., needing an open browser), exclusions (e.g., not for internal page navigation), or comparisons to siblings like 'go_back' for navigation history. Without such context, an agent might misuse it in inappropriate scenarios.

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/steel-dev/steel-mcp-server'

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