Skip to main content
Glama

getNetworkErrors

Retrieve network error logs from browser sessions to identify and troubleshoot connectivity issues.

Instructions

Check our network ERROR logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The inline handler function for the 'getNetworkErrors' MCP tool. It establishes a connection to the browser server, fetches network error logs from the '/network-errors' endpoint, formats the JSON response as text content, and marks it as an error response.
    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,
        };
      });
    });
  • Registers the 'getNetworkErrors' tool with the MCP server using server.tool(), providing a description and the inline handler function.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Check' which implies a read operation, but doesn't specify whether this requires authentication, has rate limits, returns real-time vs historical data, or affects system state. The description is too minimal for a tool that presumably accesses logs.

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 just four words, with zero wasted language. It's front-loaded with the core purpose and uses all words effectively to convey the essential function.

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?

For a log-checking tool with no annotations and no output schema, the description is insufficient. It doesn't explain what format the errors are returned in, whether they're filtered or comprehensive, time ranges covered, or how this differs from sibling logging tools. The agent lacks necessary context for effective use.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description doesn't need to compensate for any parameter gaps, and it correctly implies no required inputs for checking logs.

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 action ('Check') and resource ('network ERROR logs'), making the tool's purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'getNetworkLogs' or 'getConsoleErrors', which would require more specific scope definition.

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 'getNetworkLogs' or 'getConsoleErrors'. There's no mention of specific use cases, prerequisites, or exclusions, leaving the agent without contextual direction.

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/Sugatraj/Cursor-Browser-Tools-MCP'

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