Skip to main content
Glama
Sign In
BrowserPilot

BrowserPilot

by soulxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_network_requests

Retrieve network requests made by the browser to debug API calls, analyze web traffic, and monitor performance during automated browsing sessions.

Instructions

Get network requests

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_network_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. 'Get network requests' only implies a read operation and does not explain whether it covers the current page, all tabs, or a session, nor how results are returned or whether any state is affected.

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?

The description is maximally concise and front-loaded, with no filler or redundant detail. It is terse, but for the amount of content provided, every word is used efficiently.

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?

With no annotations, output schema, or parameters, this description is the only source of context. A three-word phrase does not adequately specify what 'network requests' means in this browser context, what the agent should expect as a result, or how the tool relates to sibling browser tools.

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 and the schema is an empty object, so schema coverage is 100%. With no inputs to document, the baseline of 4 applies; the description does not need to add parameter meaning.

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 states the action 'Get' and the resource 'network requests', which is a clear verb+resource pairing. However, it is nearly identical to the tool name, lacks scope (e.g., current page, all tabs, session), and does not explicitly differentiate itself from sibling browser diagnostic tools.

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?

There is no guidance on when to use this tool instead of browser_console_messages or browser_snapshot. No conditions, prerequisites, or exclusions are provided, leaving the agent to infer appropriate usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools