Skip to main content
Glama
nfodor

Chromium ARM64 Browser

by nfodor

navigate

Direct the Chromium ARM64 Browser to load a specific webpage URL for automation, testing, or data extraction tasks.

Instructions

Navigate to a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to navigate to

Implementation Reference

  • index.js:105-118 (registration)
    Registration of the 'navigate' tool in the MCP server's listTools response, including name, description, and input schema.
    {
      name: 'navigate',
      description: 'Navigate to a URL',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'The URL to navigate to',
          },
        },
        required: ['url'],
      },
    },
  • Input schema for the navigate tool requiring a URL string.
    inputSchema: {
      type: 'object',
      properties: {
        url: {
          type: 'string',
          description: 'The URL to navigate to',
        },
      },
      required: ['url'],
    },
  • Core handler function that launches/ensures Chromium browser and executes the Page.navigate CDP command to navigate to the specified URL.
    async navigate(url) {
      await this.ensureChromium();
      await this.sendCDPCommand('Page.navigate', { url });
      
      return {
        content: [{ type: 'text', text: `Successfully navigated to ${url}` }],
      };
    }
  • index.js:351-352 (registration)
    Dispatch/registration handler in the CallToolRequestSchema switch statement that routes 'navigate' calls to the implementation.
    case 'navigate':
      return await this.navigate(args.url);
  • MCP CallTool request handler that dispatches tool calls, including 'navigate' to its implementation.
    this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
      try {
        const { name, arguments: args } = request.params;
    
        switch (name) {
          case 'navigate':
            return await this.navigate(args.url);
          case 'screenshot':
            return await this.screenshot(args.name || 'screenshot.png', args.fullPage || false);
          case 'click':
            return await this.click(args.selector);
          case 'fill':
            return await this.fill(args.selector, args.value);
          case 'evaluate':
            return await this.evaluate(args.script);
          case 'get_content':
            return await this.getContent(args.type || 'text');
          case 'hover':
            return await this.hover(args.selector);
          case 'select':
            return await this.select(args.selector, args.value);
          case 'get_console_logs':
            return await this.getConsoleLogs();
          case 'get_console_errors':
            return await this.getConsoleErrors();
          case 'get_network_logs':
            return await this.getNetworkLogs();
          case 'get_network_errors':
            return await this.getNetworkErrors();
          case 'wipe_logs':
            return await this.wipeLogs();
          case 'get_selected_element':
            return await this.getSelectedElement();
          case 'run_accessibility_audit':
            return await this.runAccessibilityAudit();
          case 'run_performance_audit':
            return await this.runPerformanceAudit();
          case 'run_seo_audit':
            return await this.runSEOAudit();
          case 'run_best_practices_audit':
            return await this.runBestPracticesAudit();
          case 'run_nextjs_audit':
            return await this.runNextJSAudit();
          case 'run_debugger_mode':
            return await this.runDebuggerMode();
          case 'run_audit_mode':
            return await this.runAuditMode();
          case 'close_browser':
            return await this.closeBrowser();
          default:
            throw new Error(`Unknown tool: ${name}`);
        }
      } catch (error) {
        return {
          content: [{ type: 'text', text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    });
Behavior1/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 only states the action without detailing effects (e.g., page load, navigation history), error handling, or dependencies (e.g., browser state). This is inadequate for a tool that likely involves browser interaction and potential side effects.

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 with a single sentence ('Navigate to a URL') that directly conveys the core function without unnecessary words. It is front-loaded and wastes no space, making it efficient for quick understanding.

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. It doesn't cover behavioral aspects like what happens post-navigation (e.g., page load status), error scenarios, or return values. For a navigation tool in a browser context, this leaves significant gaps in understanding its full operation.

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 input schema has 100% description coverage, with the 'url' parameter fully documented in the schema. The description adds no additional meaning beyond what the schema provides (e.g., URL format or validation rules). With high schema coverage, the baseline score of 3 is appropriate as the schema handles parameter documentation.

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 URL' clearly states the action (navigate) and target (URL), making the purpose understandable. It distinguishes from siblings like 'click' or 'get_content' by focusing on URL navigation rather than interaction or retrieval. However, it doesn't specify the context (e.g., browser navigation), which slightly limits differentiation.

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., invalid URLs), or comparisons to siblings like 'get_content' for content retrieval. Usage is implied but not explicitly defined.

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/mcp-chromium-arm64'

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