Skip to main content
Glama

pilot_network

Retrieve network request data from a circular buffer to monitor and analyze web traffic during browser automation tasks.

Instructions

Get network requests from the circular buffer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clearNoClear the buffer after reading

Implementation Reference

  • The 'pilot_network' tool definition and handler implementation which retrieves network requests from a circular buffer.
    server.tool(
      'pilot_network',
      'Get network requests from the circular buffer.',
      { clear: z.boolean().optional().describe('Clear the buffer after reading') },
      async ({ clear }) => {
        await bm.ensureBrowser();
        if (clear) { networkBuffer.clear(); return { content: [{ type: 'text' as const, text: 'Network buffer cleared.' }] }; }
        if (networkBuffer.length === 0) return { content: [{ type: 'text' as const, text: '(no network requests)' }] };
        const text = networkBuffer.toArray().map(e =>
          `${e.method} ${e.url} → ${e.status || 'pending'} (${e.duration || '?'}ms, ${e.size || '?'}B)`
        ).join('\n');
        return { content: [{ type: 'text' as const, text }] };
      }
    );
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions 'circular buffer' implying a limited-size FIFO storage mechanism, but does not disclose buffer capacity, whether reads are destructive (peek vs pop), serialization format of returned requests, or whether clearing affects other operations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with verb. No redundancy. 'Circular buffer' is specific if technical. Slightly terse given absence of output schema, but wastes no words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only one optional parameter and 100% schema coverage, the description is minimally adequate. However, lacking an output schema, it omits critical information about the structure of returned network request data (headers, bodies, timing, etc.).

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?

Schema has 100% coverage for the single 'clear' parameter. Description provides minimal additional context beyond the schema, though 'circular buffer' does help frame what is being cleared. Appropriate baseline score for high schema coverage with minimal descriptive augmentation.

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?

States specific action (Get) and resource (network requests) from a specific storage mechanism (circular buffer). Distinguishes from siblings like pilot_console or pilot_storage by focusing on network traffic. Could be clearer about what 'circular buffer' means in this context.

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?

Provides no guidance on when to use this tool versus alternatives like pilot_page_html for debugging, or when the 'clear' parameter should be true versus false. No mention of typical use cases such as monitoring XHR/fetch requests.

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/TacosyHorchata/Pilot'

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