Skip to main content
Glama

getNetworkErrors

Retrieve network error logs from browser sessions to identify and troubleshoot connectivity issues, failed requests, and HTTP errors during web interactions.

Instructions

Check our network ERROR logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler and registration for the 'getNetworkErrors' MCP tool. Fetches network error logs from the browser connector server at '/network-errors' endpoint using the discovered host/port, stringifies the JSON response, and marks it as an error.
    server.tool("getNetworkErrors", "Check our network ERROR logs", async () => {
      return await withServerConnection(async () => {
        const response = await fetch(
          `http://${discoveredHost}:${discoveredPort}/network-errors`
        );
        const json = await response.json();
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(json, null, 2),
            },
          ],
          isError: true,
        };
      });
    });
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 tool checks logs, implying a read-only operation, but doesn't clarify if it requires authentication, has rate limits, returns structured or raw data, or handles errors. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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: 'Check our network ERROR logs'. It's front-loaded with the core action and resource, with zero wasted words. Every part of the sentence contributes to understanding the tool's purpose.

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 no annotations, no output schema, and 0 parameters, the description is minimal. It states what the tool does but lacks context on behavior (e.g., format of returned logs, error handling) or usage relative to siblings. For a tool in a set with multiple logging-related options, more guidance would improve completeness.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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

Purpose3/5

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

The description 'Check our network ERROR logs' specifies the action ('Check') and resource ('network ERROR logs'), making the purpose clear. However, it doesn't distinguish this tool from its sibling 'getNetworkLogs' (which likely retrieves all network logs, not just errors), leaving room for ambiguity. The description is not tautological but lacks sibling 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 siblings like 'getNetworkLogs' (for all network logs) or 'getConsoleErrors' (for console errors), nor does it specify contexts or exclusions. Usage is implied only by the tool name and description, with no explicit instructions.

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/oenius/browser-tools-mcp'

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