Mithwire MCP

browser_network_requests

Read captured fetch/XHR request metadata from a browser session to debug network calls, filter results by limit, or clear the recorded log.

Instructions

Read captured fetch/xhr request metadata.

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": {
      "session_id": "<session_id>"
    },
    "name": "browser_network_requests"
  }
}

Input Schema

Name	Required	Description	Default
`clear`	No
`limit`	No
`session_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Oct 18, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only tells the agent this is a read operation. It does not disclose that the required session_id selects a session, that limit bounds results, or that the clear parameter may clear captured data—a potentially important side effect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, but it is under-specified for a tool with three parameters and no schema descriptions. Brevity here is not necessarily appropriate given the missing operational context.

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?

Although an output schema exists so return values need not be explained, the description omits all parameter context and any behavioral nuance around clearing or session selection. For a tool with a required session_id and a clear side-effect parameter, the definition is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across all three parameters (session_id, limit, clear), and the description adds no parameter meaning whatsoever. The agent gets no explanation of the required session_id, the default limit of 120, or what clear actually does.

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 verb (Read) and resource (captured fetch/xhr request metadata), so the purpose is clear. However, it does not distinguish this tool from closely named siblings like browser_network_capture_get or browser_network_capture_status, which likely overlap in reading captured network data.

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 versus the many network-capture siblings, nor any conditions or prerequisites. The sentence only describes what it reads, leaving the agent to infer usage from context.

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

Deploy Server