Mithwire MCP

browser_network_capture_stop

Stop CDP-level network capture for a browser session and optionally clear captured data. Ends traffic recording so you can finalize or reset network traces.

Instructions

Stop CDP-level network capture.

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_capture_stop"
  }
}

Input Schema

Name	Required	Description	Default
`clear`	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.6/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 burden. It says only that capture stops; it does not disclose whether buffered data is discarded, whether the call is idempotent if no capture is running, what permissions or session state are required, or how it interacts with the existing 'clear' parameter.

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 waste, which is good, but at this level of brevity the terse text reads as under-specification rather than crispness for a tool with an undocumented parameter.

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?

An output schema exists, so return values need not be described. However, for a capture-lifecycle mutation tool with zero annotation coverage and an unexplained 'clear' flag, the description omits the behavioral and parameter context an agent needs to invoke it correctly.

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% and there are 2 parameters, yet the description explains neither. In particular, the 'clear' boolean's effect (whether capture is stopped and buffered entries are wiped) is left entirely ambiguous, and no format or constraints are given for session_id.

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 and resource ('Stop CDP-level network capture'), and the name distinguishes it from sibling capture tools (start/get/status). The 'CDP-level' qualifier adds precision about the layer being captured, though it stops short of explicitly routing the agent to or from those siblings.

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 call this versus alternatives, nor any mention that it pairs with browser_network_capture_start. An agent gets no indication of prerequisites, expected ordering, or what state the session must be in.

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

Deploy Server