moonlighting-mcp

Overview Schema Source Related Servers Discussions Admin

browser_network_request

Read-only

Retrieve headers and body for one captured browser network request by index, or extract only request/response headers or body. Use the request number from the network request list.

Instructions

Returns full details (headers and body) of a single network request, or a single part if part is set. Use the number from browser_network_requests.

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": {
      "index": "<index>"
    },
    "name": "browser_network_request"
  }
}

Input Schema

Name	Required	Description
`part`	No	Return only this part of the request. Omit to return full details.
`index`	Yes	1-based index of the request, as printed by browser_network_requests.
`filename`	No	File name to save the result to. Relative file names are resolved against the workspace root. If not provided, output is returned as text.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so no safety disclosure is needed. The description adds that the result includes headers and body and that `part` narrows the output, but it does not describe deeper behavior such as response size, formatting, or error cases. This is acceptable for a read-only tool.

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?

The description is a single focused sentence plus one essential usage pointer. No filler, and the core behavior is front-loaded before the optional part behavior.

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 simple read-only retrieval tool with one required parameter and complete schema descriptions, the description covers the essential invocation path: select a request from the list, optionally choose a part, and get full details. It does not explain output structure beyond 'headers and body,' but no output schema exists and the tool's behavior is straightforward.

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 description coverage is 100%, so the schema fully documents index, part, and filename. The description's mention of `part` and the index reference restates schema content rather than adding new meaning. Baseline 3 is appropriate.

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?

The description uses a specific verb-resource pair ('Returns full details ... of a single network request') and immediately contrasts with the plural sibling by referencing the index from browser_network_requests. This makes the tool's singular, detail-retrieval role unmistakable.

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

Usage Guidelines4/5

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

It gives clear context: use an index obtained from browser_network_requests, and optionally narrow to one part via `part`. It does not explicitly state when not to use this tool versus alternatives, but the singular-vs-list relationship to the sibling is clear enough.

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