Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

chrome_network_request

Send HTTP requests directly from a browser environment using its cookies and session context. Automate authenticated API calls tied to a specific browser profile.

Instructions

Send a network request from the browser with cookies and other browser context

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>",
      "url": "<url>"
    },
    "name": "chrome_network_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to send the request to
bodyNoBody of the request (for POST, PUT, etc.)
envIdYesEnvironment ID for the browser environment to operate.
methodNoHTTP method to use (default: GET)
headersNoHeaders to include in the request
timeoutNoTimeout in milliseconds (default: 30000)

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?

With no annotations, the description carries the full burden, and it does disclose one key trait: the request inherits browser cookies and context, implying authenticated session reuse. It says nothing about side effects of mutating methods (POST/PUT), whether the response body is returned or how errors/timeouts surface, or whether cross-origin rules apply.

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 no filler, and the differentiating cookie/context detail comes early. It is efficient, though so terse that it leaves little room for the behavioral context an unannotated mutation tool needs.

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 six-parameter tool with a nested headers object, mutating methods, and no annotations or output schema, the description is thin. An agent still cannot tell what the call returns, how failures are reported, or whether response body/headers are accessible.

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 every parameter including method, headers, timeout, and envId is already documented, and the description adds no syntax or formatting detail beyond it (e.g., whether body is JSON-encoded). The baseline of 3 applies when the schema does the heavy lifting.

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?

"Send a network request from the browser" gives a specific verb plus resource, and the qualifier "with cookies and other browser context" distinguishes it from a plain HTTP client. It remains slightly ambiguous whether it replays a captured request or issues an arbitrary new one, which is the main thing separating it from the chrome_network_capture_* 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 statement of when to use this versus chrome_network_capture_start/chrome_network_capture_stop or a raw fetch, and no prerequisites beyond the implicit need for an active browser environment. The agent must infer the use case entirely from the name.

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