Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_network_capture_start

Initiates network request capture for a web page using the Chrome webRequest API, letting you record traffic on a target URL or the active tab of a DICloak browser environment.

Instructions

Start capturing network requests from a web page using Chrome webRequest API(without responseBody)

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

Input Schema

NameRequiredDescriptionDefault
urlNoURL to capture network requests from. If not provided, uses the current active tab
envIdYesEnvironment ID for the browser environment to operate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one genuinely useful behavioral trait — capture excludes responseBody — and 'start' implies a stateful session that must later be stopped. However, it says nothing about duration, what happens if capture is already running, storage limits, or where the captured data ends up.

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?

A single front-loaded sentence with the operation, mechanism, and its key limitation; no filler. Minor cosmetic weakness (missing space before the parenthetical) and the caveat could be phrased more clearly.

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?

For a stateful capture tool with no annotations and no output schema, the description omits what an agent most needs: that a corresponding stop call is required and how to retrieve the captured requests afterward. The responseBody exclusion is the only behavioral fact given.

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 coverage is 100%, with both url and envId documented in the schema including the active-tab fallback for url. The description adds no syntax, format, or constraint detail beyond that, so the baseline of 3 applies.

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 gives a specific verb ('Start capturing') and resource ('network requests from a web page') plus the underlying mechanism (Chrome webRequest API). It clearly implies the pairing with chrome_network_capture_stop via 'start', but never names that sibling or explicitly contrasts the two.

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 when-to-use guidance at all: nothing says when to capture versus use chrome_network_request, whether capture must be paired with a stop call, or whether it can run alongside other browser actions. Usage is only inferable from the tool name.

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