Skip to main content
Glama

network_requests

Read a tab's HTTP activity—method, URL, status, and type—since it opened or was last cleared, with optional regex filtering and buffer clearing.

Instructions

Read the network requests a tab has made (method, URL, status, type) since it was opened or last cleared.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tabId": "<tabId>"
    },
    "name": "network_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoClear the buffer after reading
limitNoMost recent N, default 100
tabIdYesTab ID, from tabs_list or tab_create
patternNoRegex filter on the URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses buffer semantics — history is bounded by tab open or last clear — but never mentions that the `clear` option permanently discards that buffer, nor does it characterize latency, permissions, or truncation when hitting the default 100-item cap.

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?

A single front-loaded sentence with the resource, the scope constraint, and the return fields, with no filler. It is tight and readable; the only lost opportunity is that the buffer/clear caveat is buried in a trailing clause rather than stated as an explicit warning.

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

Completeness4/5

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

For a four-parameter read tool with 100% schema coverage and no output schema, the description covers the essentials and even names the returned fields in place of an output schema. The gap is the undisclosed destructive effect of `clear` and no mention of result capping.

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 coverage is 100%, so all four parameters are already documented in structured form; the baseline is 3. The phrase "or last cleared" adds a little meaning by tying the `clear` parameter to the buffer state, but the description adds nothing about `pattern` regex behavior or `limit` defaults beyond the schema.

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

Purpose5/5

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

States a specific verb ("Read") plus resource ("network requests a tab has made") and enumerates the returned fields (method, URL, status, type). The resource is naturally distinct from siblings like console_messages and get_page_text, so an agent can route here without ambiguity.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the scoping clause "a tab has made ... since it was opened or last cleared," which tells the agent this is a per-tab buffered history read. However, there is no explicit when-to-use vs when-not guidance and no named alternative (e.g., use console_messages for JS logs).

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