Skip to main content
Glama

network_request

Read-only

Inspect a single captured browser request by ID, including request and response headers and bodies, to debug network activity in a shared tab.

Instructions

Show one captured request in full: request and response headers, request body and response body.

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": {
      "id": "<id>"
    },
    "name": "network_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequest id from network_requests, e.g. "r42".
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
maxCharsNoBody limit, default 20000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, and the description is consistent with it ('Show'). It adds useful content scope (headers plus both bodies), but says nothing about truncation behavior, despite the schema exposing a maxChars body limit and there being no output schema to describe it.

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?

One sentence, front-loaded with the verb and scope, with a compact colon list of return contents. Every clause earns its place and there is no filler.

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?

With no output schema, the description carries the burden of describing the return value, and it does so concretely (request/response headers and bodies). It falls short only on truncation semantics tied to maxChars, which an agent calling it on a large payload would want to know.

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?

Schema description coverage is 100%, so all three parameters are documented in the schema, giving a baseline of 3; the description adds a small amount by making clear that bodies (the thing maxChars governs) are part of the payload. It adds no further detail on the id or tab parameters beyond what the schema states.

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 gives a specific verb ('Show') and a precise scope ('one captured request'), and it enumerates exactly what is included: request/response headers and bodies. That distinguishes it from the listing sibling network_requests implied by the schema's 'Request id from network_requests' note, though the description itself never names an alternative.

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 only implied: 'one captured request' suggests fetching a single item in contrast to a bulk listing, and the schema ties the id to network_requests. There is no explicit statement of when to prefer this tool over siblings or any preconditions.

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