Skip to main content
Glama
FutureAtoms

Agentic Control Framework (ACF)

by FutureAtoms

browser_network_requests

Capture and inspect browser network requests to debug API calls and resource loading.

Instructions

browser network requests

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler function for browser_network_requests tool. Monitors network requests and responses on the current page, collecting URL, method, headers, postData, status, and timestamps into page._networkRequests array. Returns the list of collected requests/responses with a count.
    async function browserNetworkRequests() {
      try {
        const page = await getPage();
        
        // Set up request monitoring if not already done
        if (!page._networkRequests) {
          page._networkRequests = [];
          
          page.on('request', request => {
            page._networkRequests.push({
              url: request.url(),
              method: request.method(),
              headers: request.headers(),
              postData: request.postData(),
              timestamp: new Date().toISOString(),
              type: 'request'
            });
          });
          
          page.on('response', response => {
            page._networkRequests.push({
              url: response.url(),
              status: response.status(),
              statusText: response.statusText(),
              headers: response.headers(),
              timestamp: new Date().toISOString(),
              type: 'response'
            });
          });
        }
    
        return {
          success: true,
          requests: page._networkRequests || [],
          count: (page._networkRequests || []).length
        };
    
      } catch (error) {
        logger.error(`Error getting network requests: ${error.message}`);
        return {
          success: false,
          message: error.message
        };
      }
    }
  • Registration of the browser_network_requests tool in the MCP tools list with a generated description.
    const browserExtras = [
      { n:'browser_navigate_back' }, { n:'browser_navigate_forward' }, { n:'browser_hover' }, { n:'browser_drag' },
      { n:'browser_select_option' }, { n:'browser_press_key' }, { n:'browser_snapshot' }, { n:'browser_console_messages' },
      { n:'browser_network_requests' }, { n:'browser_tab_list' }, { n:'browser_tab_new' }, { n:'browser_tab_select' },
      { n:'browser_tab_close' }, { n:'browser_file_upload' }, { n:'browser_wait' }, { n:'browser_wait_for' },
      { n:'browser_resize' }, { n:'browser_handle_dialog' }
    ];
    for (const b of browserExtras) {
      tools.push({ name: b.n, description: b.n.replace(/_/g,' '), inputSchema: { type:'object', properties:{} } });
    }
  • Dispatch case for browser_network_requests, calling browserTools.browserNetworkRequests() and returning the data.
    case 'browser_network_requests': data = await browserTools.browserNetworkRequests(); break;
  • Module export exposing browserNetworkRequests as part of the browserTools API.
    module.exports = {
      // Navigation
      browserNavigate,
      browserNavigateBack,
      browserNavigateForward,
      
      // Interaction
      browserClick,
      browserType,
      browserHover,
      browserDrag,
      browserSelectOption,
      browserPressKey,
      
      // Capture
      browserTakeScreenshot,
      browserSnapshot,
      browserPdfSave,
      
      // Tab management
      browserTabList,
      browserTabNew,
      browserTabSelect,
      browserTabClose,
      
      // Utilities
      browserConsoleMessages,
      browserFileUpload,
      browserWait,
      browserWaitFor,
      browserResize,
      browserHandleDialog,
      browserClose,
      browserInstall,
      browserNetworkRequests
    };
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., read-only, destructive effects, permissions required). The agent is left without essential information about 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.

Conciseness2/5

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

Although the description is short, it is not concise in a helpful way—it lacks substance and is essentially a heading. Every sentence should contribute meaning; this one does not.

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

Completeness1/5

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

Given the lack of output schema and annotations, the description must be complete. It fails to explain what 'browser network requests' means—whether it lists, streams, or filters requests. The tool appears alongside many browser tools, yet no context differentiates it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters, the input schema is fully covered. However, the description adds no value beyond the schema. While the baseline for 0 params is 4, the description is so minimal that it fails to even hint at what the tool does with its parameters.

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

Purpose1/5

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

The description 'browser network requests' is a tautology that merely restates the tool name without specifying the action performed (e.g., 'list', 'capture', 'monitor'). It fails to convey the tool's purpose clearly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 sibling tools like browser_console_messages or browser_navigate. No context about prerequisites or alternatives is given.

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/FutureAtoms/agentic-control-framework'

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