Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_network_capture_stop

Stops capturing network requests through the webRequest API for a specified browser environment and returns the collected request data.

Instructions

Stop capturing network requests using webRequest API and return the captured data

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": {
      "envId": "<envId>"
    },
    "name": "chrome_network_capture_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
envIdYesEnvironment ID for the browser environment to operate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 does disclose the underlying mechanism (webRequest API) and that captured data is returned, but it omits whether the buffer is cleared or persisted, error behavior when no capture is running, and any permission or env-state requirements.

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 action and followed by the side effect. Nothing is padded or redundant.

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?

For a simple single-parameter terminal tool with no output schema, the description is minimally adequate, but it leaves gaps an agent needs: whether the captured data is returned in the response body or via a separate retrieval tool, and whether stopping clears state for a subsequent start.

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?

There is a single required parameter (envId) with 100% schema description coverage, so the schema already explains it. The description adds no meaning about envId or its relationship to the capture session, which is the baseline expectation at this coverage level.

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?

States a specific verb and resource ('Stop capturing network requests') plus a secondary effect ('return the captured data'), which clearly distinguishes it from chrome_network_capture_start. It does not name the start tool explicitly, but 'stop' plus the sibling naming convention makes the pairing unambiguous.

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 implied rather than stated: an agent can infer this is called after chrome_network_capture_start, but the description never says so, nor does it state what happens if no capture is active or what to do with the returned data afterwards.

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