Skip to main content
Glama

navigate

Navigate to specified URLs for browser automation and web testing on ARM64 devices, enabling website interaction and UI testing.

Instructions

Navigate to a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to navigate to

Implementation Reference

  • The main handler function that executes the navigation by ensuring Chromium is running and sending a Page.navigate CDP command.
    async navigate(url) {
      await this.ensureChromium();
      await this.sendCDPCommand('Page.navigate', { url });
      
      return {
        content: [{ type: 'text', text: `Successfully navigated to ${url}` }],
      };
    }
  • Input schema defining the required 'url' parameter as a string for the navigate tool.
    inputSchema: {
      type: 'object',
      properties: {
        url: {
          type: 'string',
          description: 'The URL to navigate to',
        },
      },
      required: ['url'],
    },
  • Tool registration entry in the ListTools response, including name, description, and schema.
    {
      name: 'navigate',
      description: 'Navigate to a URL',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'The URL to navigate to',
          },
        },
        required: ['url'],
      },
    },
  • Dispatch registration in the CallToolRequest handler switch statement that routes to the navigate handler.
    case 'navigate':
      return await this.navigate(args.url);
    case 'get_content':
  • Helper function to send Chrome DevTools Protocol (CDP) commands over WebSocket, used by the navigate handler.
    async sendCDPCommand(method, params = {}) {
      return new Promise((resolve, reject) => {
        if (!wsConnection || wsConnection.readyState !== WebSocket.OPEN) {
          reject(new Error('No browser connection available'));
          return;
        }
    
        const commandId = Date.now();
        const command = { id: commandId, method, params };
    
        const timeout = setTimeout(() => {
          reject(new Error(`CDP command timeout: ${method}`));
        }, 10000);
    
        const messageHandler = (data) => {
          try {
            const response = JSON.parse(data.toString());
            if (response.id === commandId) {
              clearTimeout(timeout);
              wsConnection.off('message', messageHandler);
              if (response.error) {
                reject(new Error(`CDP error: ${response.error.message}`));
              } else {
                resolve(response.result);
              }
            }
          } catch (error) {
            // Ignore parsing errors for non-matching messages
          }
        };
    
        wsConnection.on('message', messageHandler);
        wsConnection.send(JSON.stringify(command));
      });
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't describe how it behaves: whether it waits for page load, handles errors, requires an open browser, or has side effects. 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 extremely concise at three words, front-loading the core action with zero wasted text. Every word earns its place, making it efficient for quick scanning.

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 complexity of browser navigation (which can involve loading, errors, or state changes) and the absence of both annotations and an output schema, the description is incomplete. It doesn't address behavioral expectations or return values, leaving gaps for a tool that interacts with dynamic web environments.

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. The description adds no additional meaning beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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 verb ('Navigate') and resource ('to a URL'), making the purpose immediately understandable. It doesn't distinguish from sibling tools like 'click' or 'select', but the action is specific enough for basic comprehension.

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 like 'click' or 'select', nor does it mention prerequisites or context for navigation. It's a bare statement of function without usage context.

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/nfodor/claude-arm64-browser'

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