Skip to main content
Glama

network_request

Retrieve one captured browser HTTP request by ID to inspect its headers and truncated response body; cookies and authorization headers are redacted.

Instructions

One request from read_network_requests: its headers and response body (cut at 20000 characters).

Cookies and authorization headers show as [redacted].

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

Input Schema

NameRequiredDescriptionDefault
tab_idNo
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose two important behaviors: response bodies are truncated at 20000 characters, and cookies/authorization headers are redacted. It does not say what happens for a missing request_id, whether it waits on in-flight requests, or how truncation is signalled in the output.

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?

Two tight sentences with no filler, and the most important scoping fact (single request) is front-loaded. The wording of the opening clause is slightly awkward, but nothing is wasted.

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?

There is no output schema, and the description reasonably describes the returned payload's shape and its two caveats (truncation, redaction). However, for a two-parameter tool with zero annotation and zero schema-description coverage, leaving tab_id entirely unexplained is a real gap.

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?

Schema description coverage is 0%, so the description must compensate for two undocumented parameters. It only implies that request_id selects a request; the optional tab_id parameter (nullable, default null) is never mentioned, nor is the expected request_id format or how it relates to the parent list output.

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 states a specific resource — a single network request's headers and response body — and anchors it to the sibling read_network_requests, making the singular-vs-list distinction clear. It lacks an explicit verb, but an agent can still tell exactly what it returns.

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: the phrasing 'One request from read_network_requests' suggests calling the list tool first and then drilling into one entry. It never states when to prefer this over the bulk tool or what to do if the request_id is unknown, so the agent must infer the workflow.

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