Skip to main content
Glama
nfodor

Chromium ARM64 Browser

by nfodor

get_network_errors

Retrieve network error logs to diagnose connectivity issues during browser automation and web testing on ARM64 devices with Chromium.

Instructions

Get network error logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that returns the list of stored network errors as a JSON string in the tool response format.
    async getNetworkErrors() { return { content: [{ type: 'text', text: JSON.stringify(networkErrors, null, 2) }], }; }
  • Tool schema definition including name, description, and empty input schema (no parameters required).
    { name: 'get_network_errors', description: 'Get network error logs', inputSchema: { type: 'object', properties: {}, }, },
  • index.js:373-374 (registration)
    Registration of the tool handler in the switch statement within the CallToolRequestSchema handler.
    case 'get_network_errors': return await this.getNetworkErrors();
  • index.js:255-262 (registration)
    Tool registration in the ListToolsRequestSchema response, listing the tool with its schema.
    { name: 'get_network_errors', description: 'Get network error logs', inputSchema: { type: 'object', properties: {}, }, },
  • Helper code in the Network.responseReceived event listener that populates the networkErrors array when status >= 400.
    if (message.params.response.status >= 400) { networkErrors.push(logEntry); } // Keep only last 100 entries if (networkLogs.length > 100) networkLogs.shift(); if (networkErrors.length > 100) networkErrors.shift(); }

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